[
https://issues.apache.org/jira/browse/IVY-1450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937218#comment-17937218
]
Eric Milles commented on IVY-1450:
----------------------------------
In order to stop the {{optional}} elements, you need to supply scope mappings
to your {{makepom}} task:
{code:xml}
<ivy:makepom conf=*(public)" ivyfile="..." pomfile="...">
<mapping conf="compile" scope="compile" />
</ivy:makepom>
{code}
> makepom is not including inherited confs
> ----------------------------------------
>
> Key: IVY-1450
> URL: https://issues.apache.org/jira/browse/IVY-1450
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.3.0
> Reporter: David Arthur
> Priority: Major
>
> If I have several confs that are inherited by "compile" and I want to map
> them all to the "compile" scope in the POM, I have to include them all
> explicitly.
> It seems like given configurations like:
> {code}
> <configurations>
> <conf name="compile" extends="A,B,C,D"/>
> <conf name="A" visibility="private"/>
> <conf name="B" visibility="private"/>
> <conf name="C" visibility="private"/>
> <conf name="D" visibility="private"/>
> </configurations>
> {code}
> I should be able to do a mapping like:
> {code}
> <ivy:makepom conf="compile">
> <mapping conf="compile" scope="compile"/>
> </ivy:makepom>
> {code}
> And get all the deps of A, B, C, and D mapped into the compile POM scope.
> If I include these confs like:
> {code}
> <ivy:makepom conf="*">
> {code}
> Then they are included, but they are marked as optional and they are not
> marked as the compile scope.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
