"adrian(a)jboss.org" wrote : | Another alternative would be for acme2 to declare a uses constraint | such that it could fall back to ales version 1 when required. Then everybody | would use ales version 1 with acme2's export of ales ignored. | | But that would fail in this example because it would still conflict on the scott package. OK, this makes sense, and it's more logical. But I still don't see why it would fail on scott? Or you're assuming scott package uses something from ales? Even if it would, why would that be a problem? Shouldn't there be a way to tell that in-bundle usage is a black box, and scott's usage of ales is impl detail. Would then there be a way to get runtime CCE if something ales's was exposed through scott and used in foobar? Or how do you detect this at deployment, exposing the possible conflict? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151221#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...