[
https://issues.apache.org/jira/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931920#comment-15931920
]
Karl Heinz Marbaise commented on MDEPLOY-131:
---------------------------------------------
Have you bound deploy plugin in your pom with the {{deploy-file}} goal several
times which means you can call simply {{mvn clean deploy}} and that's it?
If so you are violating the separation of concerns of a pom file cause a single
pom file should have only one concern which means produce a single artifact
(identified by groupId, artifactId, version) or maybe several but having the
same dependencies...If you need to have different dependencies this means you
should have different pom files.
Sorry to say if your customers are not familiar with slf4j than they should
read the manual...but I can understand that you like to offer them a convenient
solution which can simply being done by using different pom's with a single
concern which in result produces a multi module build.
Based on others requests..This issue is open for a long time and last comment
is of 2014..more than two years silence so it couldn't be real big
problem..apart from that there clean solutions for this which I already
described...
> 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)
