You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2010/08/11 23:51:16 UTC
[jira] Resolved: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene resolved IVY-770.
-------------------------------
Assignee: Maarten Coene
Fix Version/s: 2.2.0
Resolution: Fixed
I've committed the patch in both trunk and 2.2.x branch.
Could you please verify?
thanks a lot for the contribution!
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
> Assignee: Maarten Coene
> Priority: Minor
> Fix For: 2.2.0
>
> Attachments: apache-ivy-2.0.0-makepom-with-unit-tests.patch, apache-ivy-2.0.0-makepom.patch, IVY-770.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.