[
https://issues.apache.org/jira/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933389#comment-15933389
]
Robert Scholte commented on MDEPLOY-131:
----------------------------------------
Hi Richard,
I think we need to cool down things. When reading your story for the first time
I had the same idea as Karl Heinz. I consider suggesting a solution which
matches the current Maven behavior as a great help.
Reading your situation over again, I see your situation:
1 sourceproject results in multiple artifacts (jar + pom), meaning different
artifactIds.
I think the situation is too rare to apply the patch. A custom plugin makes
more sense.
Maybe there's good news: [~stephenconnolly] is working on a proposal for the
next major version of Maven. And one of the suggestions is to have a pom for
every uploaded artifact. Mapping this to your situation you *could* attach
every artifact with the same artifactId, but with a separate classifier.
Another option I'm thinking of right is to have multiple pom-files if the root
of your project. Maybe even with an aggregator
pom.xml (aggregator with modules pointing to every pom below)
pom-default.xml
pom-jcl.xml
pom-jul.xml
this way there's no need for multiple separate calls, no need for separate
commandline arguments.
> 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)
