I'd say we want to stick to one version of jboss-common.jar and fix the
But to avoid this taking too long, we can temporarily create a snapshot
of jboss-common.jar from 4.0
Just create a JIRA task for the snapshot to be removed by 4.0.5.CR1
Should I switch to SVN for JBossXB now?
An update on this task:
We found a problem with the cvs2svn scripts which was not correctly handling files deleted on a branch. Ruel found this when trying to build the 4.0 commons snapshot. We are triaging the bug with the cvs2svn developers.
So please continue to work on JbossXB out of CVS as usual. We will notify and do another export once we resolve the issue.
We've resolved the issues.
The svn repository is now populated with source from the common module and it is buildable.
To get the main branch:
svn co https://svn.jboss.org/repos/common/trunk/ common
To get the 4.0 branch version
svn co https://svn.jboss.org/repos/common/trunk/branches/Branch_4_0 common-4_0
I have published the artifacts which result from these builds to:
The next steps are to
1) get a verification this looks ok
2) notify the dev list
3) cutoff cvs access (if required)
4) integrate these artifacts into head and 4.0 (i've done this locally for testing, it's trivial)
This looks ok to me.
We need to work out who has commit access.
is this enough of a start?
Should be enough of a start.
WS and EJB3 guys sometimes modify JBossEntityResolver which is in the common.
This work has been completed.
Both head and the 4.0 branch are now building against the binary common artifacts rather than the cvs source.
The svn repository is also now available for use. Development should take place here from this point forward.
The above wiki should answer your initial questions, but I am available to help you with any problems that may arise.
What about the testsuite? Shoud I move the functional XB tests to the jboss-common now or wait until XB becomes a separate project (if ever).
We should not proceede with the breakup of the common project into separate projects along the lines of what Ruel did. The functional tests should be in the common module. The integration tests which validate the jbossas usage should remain in the jbossas testsuite.
Do I have the rights to commit to jboss-common? I am getting authorization failed trying to commit changes using username/password I use for jboss.com.
Alex, you should have commit rights as of Saturday. Please let me know if you are still encountering issues.
Yes, I am.
TomBen found an issue which we have resolved. I worked with Alex and he is in good shape now as well.
I've again broken up the common project into distinct subprojects. This work has been done on a branch in subversion and is ready to be merged into the trunk.
These are radical file structure changes, so I want to make sure everyone is comfortable before I commit them in.
These changes seperate jbossxb, the common core, and the logging projects as Scott described. The jars which are built correspond to each of the projects. These projects are maven buildable.
I would like to merge these changes in tomorrow.