[
https://issues.apache.org/jira/browse/MDEPLOY-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965802#comment-17965802
]
Olivier Lamy commented on MDEPLOY-255:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#289|https://github.com/apache/maven-deploy-plugin/issues/289].
> altDeploymentRepository is broken on mingw/cygwin/windows
> ---------------------------------------------------------
>
> Key: MDEPLOY-255
> URL: https://issues.apache.org/jira/browse/MDEPLOY-255
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Reporter: Valentin titov
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I'm trying to deploy some patched plugin from github to my internal
> repository.
> maven-deploy-plugin has nice altDeploymentRepository parameter for such cases.
> I'm using bash from msys2 (it's windows) and when run mvn with this
> parameter:
> {code:bash}
> mvn install \
> org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy\
>
>
> -DaltDeploymentRepository=default::http://nexus:8080/nexus/content/repositories/some_repo
> {code}
> I get error
> {noformat}
> [INFO] Using alternate deployment repository
> default;http://nexus;8080\nexus\content\repositories\some_repo
> {noformat}
> ...
> [ERROR] Invalid syntax for alternative repository. Use "id::::url".
> {noformat}
> This happens because URL part of parameter becomes broken when read as a
> string parameter. I do not know if it happens inside ProjectDeployerRequest
> or not, I do not know if 'native' mvn bat/cmd has the same problem.
> I suppose that URL should be processed as URL, not string, so I suggest
> adding separate parameters:
> altDeploymentRepositoryId and altDeploymentRepositoryURL
> see proposed fix in PR#6
> https://github.com/apache/maven-deploy-plugin/pull/6
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
