[
https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832305#action_12832305
]
Aaron Hachez commented on IVY-770:
----------------------------------
This issue is also in 2.1.0 release
> 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.
