Component
MCP Capability (polychro-capability)
Polychro Version
0.1.0-SNAPSHOT
Operating System
Windows 11
Description
Actual behavior:
polychro-capability/pom.xml still declares the talend-restlet repository with a comment saying it is required to resolve org.restlet:org.restlet:2.7.0-m2 for the workaround around naftiko/framework#433.
Current verification shows that this specific Restlet artifact is already available from Maven Central, while the direct artifact path on https://maven.restlet.talend.com/ returns 404.
This leaves the module with a stale repository declaration and a misleading comment about why the repository is needed.
Expected behavior:
If org.restlet:org.restlet:2.7.0-m2 is fully resolvable from Maven Central, polychro-capability should not declare the extra talend-restlet repository. The comment should also be updated so it matches the real dependency resolution behavior.
Steps to Reproduce
- Inspect
polychro-capability/pom.xml and locate the talend-restlet repository entry under <repositories>.
- Resolve the dependency from Maven Central:
mvn -q org.apache.maven.plugins:maven-dependency-plugin:3.8.1:get "-Dartifact=org.restlet:org.restlet:2.7.0-m2" -Dtransitive=false
- Check the artifact URLs:
- Maven Central POM:
https://repo1.maven.org/maven2/org/restlet/org.restlet/2.7.0-m2/org.restlet-2.7.0-m2.pom
- Maven Central JAR:
https://repo1.maven.org/maven2/org/restlet/org.restlet/2.7.0-m2/org.restlet-2.7.0-m2.jar
- Talend repo POM path:
https://maven.restlet.talend.com/org/restlet/org.restlet/2.7.0-m2/org.restlet-2.7.0-m2.pom
- Observe that Maven Central serves the artifact, while the Talend URL does not for that path.
Logs & Stacktrace
Verification performed locally:
- Maven Central POM: HTTP 200
- Maven Central JAR: HTTP 200
- Talend repo artifact path: HTTP 404
mvn dependency:get for org.restlet:org.restlet:2.7.0-m2: exit code 0
Agent Context (optional)
agent_name: GitHub Copilot
llm: GPT-5.4
tool: VS Code Copilot coding agent
confidence: high
source_event: review of polychro-capability/pom.xml repository declaration
discovery_method: code_review
files_suspected:
- polychro-capability/pom.xml
Component
MCP Capability (polychro-capability)
Polychro Version
0.1.0-SNAPSHOT
Operating System
Windows 11
Description
Actual behavior:
polychro-capability/pom.xmlstill declares thetalend-restletrepository with a comment saying it is required to resolveorg.restlet:org.restlet:2.7.0-m2for the workaround aroundnaftiko/framework#433.Current verification shows that this specific Restlet artifact is already available from Maven Central, while the direct artifact path on
https://maven.restlet.talend.com/returns404.This leaves the module with a stale repository declaration and a misleading comment about why the repository is needed.
Expected behavior:
If
org.restlet:org.restlet:2.7.0-m2is fully resolvable from Maven Central,polychro-capabilityshould not declare the extratalend-restletrepository. The comment should also be updated so it matches the real dependency resolution behavior.Steps to Reproduce
polychro-capability/pom.xmland locate thetalend-restletrepository entry under<repositories>.mvn -q org.apache.maven.plugins:maven-dependency-plugin:3.8.1:get "-Dartifact=org.restlet:org.restlet:2.7.0-m2" -Dtransitive=falsehttps://repo1.maven.org/maven2/org/restlet/org.restlet/2.7.0-m2/org.restlet-2.7.0-m2.pomhttps://repo1.maven.org/maven2/org/restlet/org.restlet/2.7.0-m2/org.restlet-2.7.0-m2.jarhttps://maven.restlet.talend.com/org/restlet/org.restlet/2.7.0-m2/org.restlet-2.7.0-m2.pomLogs & Stacktrace
Verification performed locally:
mvn dependency:getfororg.restlet:org.restlet:2.7.0-m2: exit code 0Agent Context (optional)