You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Paul Wardrip (JIRA)" <ji...@apache.org> on 2008/03/13 17:12:24 UTC
[jira] Created: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
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
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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: (was: IVY-770.patch)
> 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, 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: IVY-770.patch
Patch updated against trunl (2010/07/19)
> 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, 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: IVY-770.patch
I think it would be easier to start with basic support where the artifact is specified as part of the makepom task.
And then exclude the mappings that aren't needed for the artifact in question.
The attached patch implements this JIRA + IVY-1005 , which makes mapping multiple Ivy artifacts to different Maven pom files a lot easier in my view.
> 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, 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: (was: IVY-770.patch)
> 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, 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Paul Wardrip (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Wardrip updated IVY-770:
-----------------------------
Attachment: apache-ivy-2.0.0-makepom.patch
A patch to handle multiple artifact projects in IvyMakePom
> 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.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.
[jira] Commented: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897763#action_12897763 ]
Jesper Pedersen commented on IVY-770:
-------------------------------------
The "scope" attribute on a <dependency> doesn't get mapped correctly -- it turns into an "<optional>true</optional>" instead.
Also the <repository ... url="xyz"> doesn't get mapped to <url>xyz</url>, but we can take that in another JIRA...
> 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: IVY-770.patch
> 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, 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Mandie Smith (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mandie Smith updated IVY-770:
-----------------------------
Attachment: apache-ivy-2.0.0-makepom-with-unit-tests.patch
Attaching an updated patch with source and unit tests
> 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.
[jira] Commented: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897785#action_12897785 ]
Jesper Pedersen commented on IVY-770:
-------------------------------------
I can't read correctly -- its the "scope" attribute through
<mapping conf="myconf" scope="runtime"/>
instead.
> 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: IVY-770.patch
New version which allows extra dependencies to be added to the generated pom file. This could f.ex. be other artifacts produced in the Ivy setup.
> 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, 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.
[jira] Commented: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Aaron Hachez (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Mandie Smith (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765193#action_12765193 ]
Mandie Smith commented on IVY-770:
----------------------------------
I tested adding the following to my ivy.xml publications:
<publications>
<artifact type="pom" />
<artifact type="jar" />
<artifact m:classifier="sources" type="source" ext="jar" />
</publications>
When I generate the pom using the patched ivy code I see filename.jar, filename.pom and filename-sources.jar created. There's no additional pom created for the source jar.
> 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.
[jira] Updated: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Jesper Pedersen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesper Pedersen updated IVY-770:
--------------------------------
Attachment: (was: IVY-770.patch)
> 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.
[jira] Commented: (IVY-770) MakePom task handling of mulitple
artifacts for Maven2
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674073#action_12674073 ]
Maarten Coene commented on IVY-770:
-----------------------------------
What will happen when the ivy.xml file also declares sources and javadocs artifacts?
> 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.