[
https://issues.apache.org/jira/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934013#comment-15934013
]
Richard Sand commented on MDEPLOY-131:
--------------------------------------
Hi Robert - i admit my frustration is showing. But my question is still
unanswered - forget my use case for a moment. Forget I mentioned anything about
deploying multiple shaded artifacts. Just tell me your opinion on the following:
1) the deploy module does not have the ability to inherit the URL from the
project - this is a useful feature to have and is doable with a dozen lines of
code and an option to enable it
2) the patch is here already
3) including me, there are 5 people who have asked for this feature on this
ticket
Why would you *not* accept it?
> use default repository when no url specified
> --------------------------------------------
>
> Key: MDEPLOY-131
> URL: https://issues.apache.org/jira/browse/MDEPLOY-131
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy-file
> Reporter: raymond domingo
> 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
(v6.3.15#6346)
