[MDEPLOY-159] deploy:deploy-file should use default values from pom.xml

[jira-importer]

Robert Zanzerkia opened MDEPLOY-159 and commented

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.

---

Affects: 2.7

Remote Links:

• GitHub Pull Request #219
  

[jira-importer]

Martin Todorov commented

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.

[jira-importer]

Robert Scholte commented

If that would be the case, then it shouldn't be too hard to upload the file as part of the standard deploy. If there's an additional file you'd like to attach and deploy, please use the build-helper:attach-artifact