[ http://jira.codehaus.org/browse/MNG-1388?page=comments#action_72448 ] Milos Kleint commented on MNG-1388: -----------------------------------
since profiles are identified by ids, it will probably happen that these IDs will clash in completely unrelated 3rd party libraries. maybe the scope of dependency pom profile triggering should be limuted to the same groupId? > Transitive Dependencies in a profile are not used > ------------------------------------------------- > > Key: MNG-1388 > URL: http://jira.codehaus.org/browse/MNG-1388 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle > Affects Versions: 2.0 > Environment: Windows XP using Maven 2.0. > Reporter: Damian Bradicich > Fix For: 2.1 > > > 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. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
