I have dropped the plugins/ directory, promoting those modules to regular peers to the build module. I have also added a common module, which will hold the bits from server which aren't really specific to anything.
This is the start of some changes to better isolate the core JBoss system from plugin-like components. The concept here is to have one module which contains only the basic GPA kernel components, deployment framework and integration APIs. * * * If you have any changes on the moved modules you can still commit them in there current location, as their location in the repository has not changed. You will need to re-checkout jboss-all or if you are on a low speed line you can update your workspace by hand: from jboss-all/: # commit any changes you have in plugins/* # edit CVS/Entries and remove all the plugins/* entries rm -rf plugins cvs get -d varia contrib/varia cvs get -d jetty contrib/jetty cvs get -d catalina contrib/catalina cvs get -d jboss.net contrib/jboss.net cvs get -f common jboss-common cvs update -Pd This should get your workspace up to date (unless I forgot something). I am assuming that the win32 folks can figure out how to do this with out explicit instructions. If I am wrong (about this) let me know. Let me know if you have any problems. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
