Look, the legacy branches are not dead (2.2, 2.4) and the modules file is not versioned across branches, so renaming jboss to jboss-all breaks the 2.4 build. Restore the aliases and live with them until 2.4 is as old and crusty as windows 95.
A co of jboss needs to simply co the jboss module. This how the build process is documented in the book and I'm not going to change it or the current 2.4 source releases. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
