[
https://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281933#comment-281933
]
Ivan Bondarenko commented on MNG-1388:
--------------------------------------
We are also waiting for this bug solve (have issue similar to described in
MNG-4985).
We have a lot of modules, which form a hierarchy (3 or 4 levels). Modules can
be built with classifiers ("release", "debug" etc). When war project references
these modules, transitive dependencies without any classifiers are used.
In fact that makes "classifier paradigm" useless.
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
