merge-maven-repos goal is parsing tar file contents thinking it's a HTML page about wagon-maven-plugin HOT 7 CLOSED

After adding a HAProxy rule returning 404 to requests ending in /javascript:void(0) the plugin is failing with:

[ERROR] Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:1.1-SNAPSHOT:merge-maven-repos (default-cli) on project standalone-pom: Error during performing repository copy: Illegal character in path at index 176: https://jenkins.acme-internal.com:3000/plugin/repository/project/acme-Installer-DSL/Build/1904/repository/com/acme/ui/29.4.0-SNAPSHOT/ui-29.4.0-20161207.115106-1904.tar/' + realUrl + '/ -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.mojo:wagon-maven-plugin:1.1-SNAPSHOT:merge-maven-repos (default-cli) on project standalone-pom: Error during performing repository copy

It's because of a javascript file within the .tar package with a line containing return '<a href="' + realUrl + '">'

from wagon-maven-plugin.

related to #7

wagon html support is very dumb as well

from wagon-maven-plugin.

Hi @jakub-bochenski , after several months...

Do you still got the problem ? I can try to help but I would need a project to test the defect. Thanks

from wagon-maven-plugin.

@tchemit I gave up on the wagon plugin completely in favour of the deployer pom hack

from wagon-maven-plugin.

from wagon-maven-plugin.

Well it gets the job done.

This required a change from a pull (running maven on the receiving end) to a push.
First I deploy the build results to a local repository with the help of -DaltDeploymentRepository=file::default::file://$WORKSPACE/.m2repo. Then I run the deployer pom on $WORKSPACE/.m2repo

from wagon-maven-plugin.

This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.

from wagon-maven-plugin.