[
https://issues.apache.org/jira/browse/WAGON-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116050#comment-15116050
]
RomanS commented on WAGON-450:
------------------------------
Sure we do have Artifactory installation and normal in-house repo. It's just
much easier to use, you do not need to be connected to VPN or perform local
install before project build.
non-maven-jar-plugin looks even worse to me.
Regarding '%2F': my usecase is Jankins and
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin with multibranch
configuration. It creates CI job dynamically for any new branch and name it
accordingly.
So if I create branch named 'enhancement/great_new_feature' - job workspace
directory gets name 'enhancement%2Fgreat_new_feature'
> Directory name with escaped slashes is not handled correctly
> ------------------------------------------------------------
>
> Key: WAGON-450
> URL: https://issues.apache.org/jira/browse/WAGON-450
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-file
> Affects Versions: 2.10
> Environment: RHEL6 x64
> Reporter: RomanS
>
> Project is located in directory /a/b%2Fc and has file protocol repository
> reference:
> {code:xml}
> <repository>
> <id>project.local</id>
> <name>project</name>
> <url>file:${project.basedir}/repo</url>
> </repository>
> {code}
> During build it fails with: [ERROR] Failed to execute goal on project
> core-api: Could not resolve dependencies for project xxxxxxxxx: Failed to
> collect dependencies at xxxxxxxxxxxx:1.0-SNAPSHOT: Failed to read
> artifact descriptor for xxxxxxxxx:1.0-SNAPSHOT: Could not transfer artifact
> xxxxxxxx:1.0-SNAPSHOT from/to project.local (file:/a/b%2Fc/repo): Repository
> path /a/b/c/repo does not exist, and cannot be created. -> [Help 1]
> Workaround: rename project directory to smth w/o "%2F".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)