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

Olivier Lamy commented on MDEPLOY-131:
--------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-deploy-plugin#468|https://github.com/apache/maven-deploy-plugin/issues/468].
 Please visit the GitHub issue to view further activity, add comments, or 
subscribe to receive notifications.

> use default repository when no url specified
> --------------------------------------------
>
>                 Key: MDEPLOY-131
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-131
>             Project: Maven Deploy Plugin (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: deploy:deploy-file
>            Reporter: raymond domingo
>            Priority: Major
>              Labels: contributers-welcome
>         Attachments: DeployFileMojo.java, 
> maven-deploy-useProjectRepo-20170319.patch, 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 was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to