[
https://issues.apache.org/jira/browse/MNG-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17230562#comment-17230562
]
Delany commented on MNG-7017:
-----------------------------
I set a property
_<repo.thirdparty>${build.remote}/repository/${build.name}-endorsed</repo.thirdparty>_
and then use that in _<repositories><repository><url>${repo.thirdparty}</url>_
It makes it easier to override. That much is fine. Now I want to deploy to the
same repository.
I create a new profile with
_<distributionManagement><repository><url>${repo.thirdparty}</url>_ which I
only activate when provisioning repo.thirdparty with my static JARs. But the
deploy-file goal cannot access this URL.
> better deploy-file integration
> ------------------------------
>
> Key: MNG-7017
> URL: https://issues.apache.org/jira/browse/MNG-7017
> Project: Maven
> Issue Type: Improvement
> Components: Deployment
> Affects Versions: 3.6.3
> Reporter: Delany
> Priority: Minor
>
> I have a script which deploys hundreds of static JARs to a Nexus repo. I use
> the deploy-file goal, which requires the *url* and *repositoryId* properties.
> Currently I have to hard-code these into the script.
> I want to be able to use the repository url and id I set in the
> distributionManagement of my project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)