"adrian(a)jboss.org" wrote : I see your difficulty, but for the reasons stated above, | we can't just implicitly start exporting the default package | since that could reveal "module private" classes that the user doesn't want to be shared. | | Wouldn't it make more sense to have these "java.xxx proxies" in some jboss aop | package that its classloader explicitly exports and define then against jboss aop's classloader? | I would have less qualms about an org.jboss.aop.xxx package automatically exported by user classloaders since it is unlikely to be a user package and it is trivial to warn/document that it happens if you use choose to use jboss aop. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204762#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...