[
https://jira.codehaus.org/browse/MDEPLOY-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322572#comment-322572
]
Martin Todorov commented on MDEPLOY-159:
----------------------------------------
The deploy:deploy-file goal is mainly meant for use from the console with
pomless projects. For example, if you have a non-mavenized Java library which
you would like to have deployed to your repository.
I think this would be a change of behaviour. There could, however be a property
which could be passed in that tells Maven to use a pom.xml (if such is
present). However, in the majority of the cases, this will most-likely not be
so.
> deploy:deploy-file should use default values from pom.xml
> ---------------------------------------------------------
>
> Key: MDEPLOY-159
> URL: https://jira.codehaus.org/browse/MDEPLOY-159
> Project: Maven 2.x and 3.x Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy-file
> Affects Versions: 2.7
> Reporter: Robert Zanzerkia
> Priority: Minor
>
> Currently deploy-file requires all of below arguments.
> -Durl
> -DrepositoryId
> -DartifactId
> -Dversion
> -Dpackaging=zip
> -Dfile=./target/uCMDB-PatternDev-0.0.1-SNAPSHOT-packages.zip
> Other than the file argument it should default to values defined in project
> pom.xml IF not defined on the command line.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
