[
https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878778#action_12878778
]
Maarten Coene commented on IVY-770:
-----------------------------------
I'm not convinced this should be solved like this.
Ivy supports multiple artifacts for a module, maven does not. Perhaps it's
better to raise an exception when trying to convert such a module?
Mapping multiple artifacts to multiple maven modules isn't the same!
Using your example: adding a dependency in Ivy on your module is like this:
<dependency org="myorg" name="mymodule" rev="1.0" />
But when the POM is created like this, the dependency-declaration must be
rewritten to point to the artifacts directly:
<dependency org="myorg" name="artifact-core" rev="1.0" />
<dependency org="myorg" name="artifact-util" rev="1.0" />
Another approach which maybe could solve some (but not all) issue could be
making use of the maven-jar-plugin in combination with the 'classifier' element.
I'm not a maven user, so I don't know if this would help, but maybe it's worth
investigating?
Maarten
> MakePom task handling of mulitple artifacts for Maven2
> ------------------------------------------------------
>
> Key: IVY-770
> URL: https://issues.apache.org/jira/browse/IVY-770
> Project: Ivy
> Issue Type: Improvement
> Components: Maven Compatibility
> Affects Versions: 2.0.0-beta-2
> Reporter: Paul Wardrip
> Priority: Minor
> Attachments: apache-ivy-2.0.0-makepom-with-unit-tests.patch,
> apache-ivy-2.0.0-makepom.patch
>
>
> Maven2 won't create more than one uniquely named artifact for a project,
> unless you set the packaging to "pom". Then you have a separate pom for each
> of the artifacts, referencing the project pom with a parent tag. They would
> get deployed like this:
> /myorg/mymodule/1.0/mymodule-1.0.pom
> /myorg/artifact-core/1.0/artifact-core-1.0.pom
> /myorg/artifact-core/1.0/artifact-core-1.0.jar
> /myorg/artifact-util/1.0/artifact-util-1.0.pom
> /myorg/artifact-util/1.0/artifact-util-1.0.jar
> Resolution: Change MakePom task to build separate poms when it detects
> multiple uniquely named artifacts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
