Tomorrow, we are going to promote the jboss-common module to
an independent project housed in subversion. If you are an active
developer on this module, please check in any work to cvs. What this means for you: The common module will become its own project. This is
similar to the extraction performed for remoting and cache. The key
difference is that the new project will be housed in subversion rather than
cvs. The code for common will then be integrated into JBossAS via the
thirdparty dependency mechanism. I’ve setup a wiki page which details the “anticipated”
questions. It details the subversion usage procedures: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCommonProject Ruel Loehr JBoss QA -- |
All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development