[ 
https://issues.apache.org/jira/browse/MNG-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17230535#comment-17230535
 ] 

Michael Osipov commented on MNG-7017:
-------------------------------------

This seems to be a contradiction. Manually deploying JARs means that they are 
not Maven managed. The POM will be generated on the repo. In which POM do you 
want to store those attributes?

> 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)

Reply via email to