[ https://issues.apache.org/jira/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784624#comment-16784624 ]
Igor Tykhyy commented on MNG-1388: ---------------------------------- I'd also like to see this issue fixed (though I am not sure I could fix it myself). I'd like profiles to apply to *not only dependencies*, but also *child-modules* (specified under {{<modules>}}). {{A}} {{ - B (child-module)}} {{ - C (child-module)}} Doing {code:java} mvn clean install -Psome-profile {code} should apply the profile {{some-profile}} on *A* as well as on *B* and *C*, running the profile in each module containing it. At least for me it does not work - especially not if modules are stored in profiles themselves (I only need some modules to be built in order to deploy them; aggregator-project-packaging is set to _pom_). > Transitive Dependencies in a profile are not used > ------------------------------------------------- > > Key: MNG-1388 > URL: https://issues.apache.org/jira/browse/MNG-1388 > Project: Maven > Issue Type: Bug > Components: Plugins and Lifecycle > Affects Versions: 2.0 > Environment: Windows XP using Maven 2.0. > Reporter: dbradicich > Priority: Major > > 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 (v7.6.3#76005)