jira-importer commented on issue #237: URL: https://github.com/apache/maven-deploy-plugin/issues/237#issuecomment-2771517606
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented After some digging I discovered that it's `org.apache.maven.wagon.PathUtils.basedir(String)` which is responsible for the translation of the repository directory. A simple junittest like this succeeds: ``` assertEquals( "/share/", PathUtils.basedir( "file://host/share/" ) ); ``` The downloading/uploading output is coming from the `org.apache.maven.cli.transfer.AbstractMavenTransferListener`, which does the following: ``` out.println( message + ": " + event.getResource().getRepositoryUrl() + event.getResource().getResourceName() ); ``` ``` out.println( type + ": " + resource.getRepositoryUrl() + resource.getResourceName() + " (" + len + throughput + ")" ); ``` So here the filepath is concatenated instead of calculated, because the `resource` is a generic class for all kinds of transfers. The behavior depends on Wagon, which could change. For that reason I'd prefer not to add warnings. IMO the best solution would be an extra field to the `org.eclipse.aether.transfer.TransferResource`, which holds the (calculated) resourceTarget. For now I could add a debug-line which shows the calculated repository path. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
