JBoss Module Information
The JBossAS source code has been migrated to Subversion. Please see the following link:
http://wiki.jboss.org/wiki/Wiki.jsp?page=SubversionMigrationGuide
The remainder of the is page is kept strictly for historical reasons.
When doing a checkout from cvs you will specify a module name. Depending on the particular version of jboss you wish to check out you will need to make sure you have the correct module name. The following is the general rule - if in doubt, always check against http://fisheye.jboss.com/viewrep/JBoss/CVSROOT/modules.
JBoss Version | CVS Module |
|---|---|
<= 3.2.7 | jboss-3.2 |
> 3.2.7 | jboss-3.2.x |
< 4.0.3 RC1 | jboss-4.0 |
>= 4.0.3 RC1 | jboss-4.0.x |
3.2 development | jboss-3.2.x |
4.0 development | jboss-4.0.x |
5.0 development | jboss-head |
Examples:
Tag | JBoss Version | CVS Module |
|---|---|---|
JBoss_3_2_6 | 3.2.6 | jboss-3.2 |
JBoss_3_2_7 | 3.2.7 | jboss-3.2 |
JBoss_4_0_0 | 4.0.0 | jboss-4.0 |
JBoss_4_0_2 | 4.0.2 | jboss-4.0 |
JBoss_4_0_3_RC1 | 4.0.3RC1 | jboss-4.0.x |
Exceptions
As noted above, this is just the general rule. There are special modules and exceptions, e.g. this
Tag | JBoss Version | CVS Module |
|---|---|---|
JBoss_3_2_1 | 3.2.1 | jboss-3.2.1 |
What is the difference beetween a .x module name and one that does not have it?
The modules which have the .x suffix will not check out a thirdparty directory, the ones that do not have the .x suffix, will. Older versions of JBoss require a thirdparty folder to be checked out from cvs in order to build.
Related:
JBossBuild
Referenced by:
Comments