[
https://issues.apache.org/jira/browse/IVY-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887677#action_12887677
]
Maarten Coene commented on IVY-1005:
------------------------------------
Sorry for the late response, but to make this task more consistent with the
other Ivy tasks, I think we should add a "conf" attribute to the "makepom"
element to allow you to specify which configurations should be included. This
attribute would default to "*".
So if the module has 3 configurations (default,runtime,test) and we want to
exclude the test configuration, we could have somehting like:
{code:xml}
<ivy:makepom ivyfile="${basedir}/path/to/ivy.xml"
pomfile="${basedir}/path/to/module.pom" conf="default,runtime">
<mapping conf="default" scope="compile"/>
<mapping conf="runtime" scope="runtime"/>
</ivy:makepom>
{code}
> makepom: map to none
> --------------------
>
> Key: IVY-1005
> URL: https://issues.apache.org/jira/browse/IVY-1005
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 2.0-RC2
> Reporter: Stepan Koltsov
> Attachments: IVY-1005.patch
>
>
> {code}
> <makepom ...>
> <mapping conf="test" nowhere="true"/>
> </makepom>
> {code}
> So all dependencies in configuration "test" will not present in generated
> pom.xml.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
