[
https://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340233#comment-340233
]
Wiebke Timm commented on MNG-1388:
----------------------------------
Not sure what you mean by "set those in the profiles". If you set the property
in some parent, you would need a different parent (for that platform's profile)
for different platforms. But that doesn't solve cases with managed dependencies:
For managed dependencies, a whole subtree is built with a certain platform
(i.e. classifier) that's different from the platform of the rest of the tree,
but still must be unique within that subtree. This cannot be addressed properly
without modeling of transitive dependencies.
In any case, we have tried using properties and failed. We are using a
workaround with environment variables and that still can't properly deal with
the subtree problem described above.
> Transitive Dependencies in a profile are not used
> -------------------------------------------------
>
> Key: MNG-1388
> URL: https://jira.codehaus.org/browse/MNG-1388
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0
> Environment: Windows XP using Maven 2.0.
> Reporter: Damian Bradicich
> Fix For: Issues to be reviewed for 3.x
>
>
> I have a jar project file that defines a dependency inside a certain profile.
> If I then include that project inside of another war project, the
> dependencies defined in the jar project's profile isn't getting transferred
> over to the war.
> Ie we have this:
> A depends on SQL or Oracle depending on profile
> B depends on A.
> If sql profile is active, I would expect that when I build B, it pulls
> the transitive dependancy on sql from A.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
