Re: [forge-dev] Changes to Forge Modules structure

The only reason I can see this affecting Koen is if he (in his tools module) referenced the "org.jboss.forge.shell-api" module directly, which has been moved to "org.jboss.forge.shell.api" Or if there are classes that he referenced that were available because of modularity errors, but now are not. What I would do in this case, however, is simply make both modules optional="true", which should prevent any breakage, then whichever is available will be used. If neither are available, it wasn't going to work anyway ;) I would try to make these changes for M4 even if you don't use the new SNAPSHOT version of Forge - sorry guys. I did not know :( Mailing list I should join? Nothing has changed with regard to how plugins are installed, but what *has* changed is what happens to plugins *when* they are installed - again, just to enable the proper modularity. But this should not be visible to the end user (or Tools.) ~Lincoln On Thu, Oct 20, 2011 at 9:40 AM, Max Rydahl Andersen < max.andersen(a)redhat.com&gt; wrote: -- Lincoln Baxter, III http://ocpsoft.com http://scrumshark.com "Keep it Simple"