"david.lloyd(a)jboss.com" wrote : | Far simpler than designing a plugin mechanism for restrictions is to simplify the API so that you just give it the input streams of classes you want to index. Simplfying the API is usually preferable to adding an abstraction. | A? What kind of nonsense is this? And how do you plan on providing this streams? Via abstraction!!!! Or how else are you gonna know which one's should or shouldn't be scanned? Should I list them by hand, all of the 1M classes? Or what about if tomorrow Sun speeds up its modules impl, and we all start doing module-info.java? "david.lloyd(a)jboss.com" wrote : | The specifications for many of our components (like EJB 3.1) tell us that we can't rely on this, or at least that's my understanding from the developer meeting when we decided we had to do it this way. Then I would say this is their problem. Who ever doesn't have automated build, has either just started programming or is moro.... The first one's don't need this feature yet, the 2nd one's don't deserve it. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261322#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...