[ http://jira.codehaus.org/browse/MEAR-39?page=comments#action_77260 ] Jonas Olsson commented on MEAR-39: ----------------------------------
This is something I do not observe. Quite the opposite, I removed an EJB-jar duplication (once in root and once in APP-INF\lib) by making the dependency "provided" where appropriate. "provided" dependencies of the EAR project itself are also excluded. > Scope=provided is not respected > ------------------------------- > > Key: MEAR-39 > URL: http://jira.codehaus.org/browse/MEAR-39 > Project: Maven 2.x Ear Plugin > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Olle Hallin > Priority: Critical > > The produced ear contains *all* transitive dependencies, even those with > scope=provided (and their dependencies). > This leads not only to a bloated ear. What is worse is that it also prohibits > deployment in JBoss due to class loading conflicts. -- 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
