[
https://jira.codehaus.org/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354701#comment-354701
]
Arne Brix commented on MDEPLOY-131:
-----------------------------------
I have a similar usecase. We use the replacer plugin to modify our pom file
(using a jenkins env-variable) before it is being deployed.
With the old deploy plugin we could simply set the pomFile property to specify
the path of the changed pom for deploy:deploy but now we must use deploy:file
and that's not really practical if one has different repositories for releases
and snapshots.
So please let deploy:deploy honor the pomFile property as before or add
automatic repository selection to deploy:file.
> use default repository when no url specified
> --------------------------------------------
>
> Key: MDEPLOY-131
> URL: https://jira.codehaus.org/browse/MDEPLOY-131
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)
