[
https://jira.codehaus.org/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292471#comment-292471
]
Darshak Thakore commented on MDEPLOY-131:
-----------------------------------------
i agree that the patch shouldn't force existing behavior, however the need to
let deploy-file use the default repositories from the repositoryManagement
section is also very important. Specifically since the deploy goal does not
allow specifying secondary artifacts (eg. a zip file)
> use default repository when no url specified
> --------------------------------------------
>
> Key: MDEPLOY-131
> URL: https://jira.codehaus.org/browse/MDEPLOY-131
> Project: Maven 2.x and 3.x Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy-file
> Reporter: raymond domingo
> Labels: contributers-welcome
> Attachments: DeployFileMojo.java, patch_deploy_file_mojo.diff
>
>
> When using the deploy goal there is no need to specify the url of the
> repository.
> When using deploy-file you DO need to specify the url. This is a problem,
> because during development I like to deploy to snapshot repository and when
> releasing i deploy to release repository and I can't add this logic to the
> pom.
> Thas is why I like the url paramter to become optional (backwards compatible)
> and add default behaviour when it is null. It should just like the deploy
> plugin use the default repository. Snapshot for snapshots and release for
> none snapshot versions.
> I added a patch file fixing this.
> I also added complete source of patched Mojo
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
