The distributed seam-bom shouldn't describe any non-seam dependencies directly ------------------------------------------------------------------------------ Key: SEAM-110 URL: https://issues.jboss.org/browse/SEAM-110 Project: Seam 3 Distribution Issue Type: Enhancement Affects Versions: 3.1.0.Beta3 Reporter: Geoffrey De Smet The seam-bom currently also describes other dependency versions such as drools-core and javassist. If the seam-bom is meant to be used by other projects (=users), that's a bad thing, because it overwrites the version that they are using. For example: {code} seam-bom declares: - drools-core 5.1.0.Final - javassist 3.0.14-GA droolsjbpm-parent declares: - drools-core 5.3.0.Final - javassist 3.0.15-GA guvnor extends droolsjbpm-parent guvnor-webapp extends guvnor and dependencyManagement imports seam-bom and declares - drools-core - javassist Result: guvnor-webapp gets which is wrong - drools-core 5.1.0.Final - javassist 3.0.14-GA {code} If seam-bom would only declare seam-* dependencies, then everything would be fine: those dependencies have the correct dependency versions they want (drools-core 5.1.0.Final and javassist 3.0.14-GA) but a multiproject can easily overwrite them to a higher version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira