-
60. Re: Breaking up common in jboss-head
adrian.brock May 31, 2006 12:42 PM (in response to starksm64)I'd say we want to stick to one version of jboss-common.jar and fix the
problems.
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 -
61. Re: Breaking up common in jboss-head
aloubyansky Jun 2, 2006 12:06 PM (in response to starksm64)Should I switch to SVN for JBossXB now?
-
62. Re: Breaking up common in jboss-head
ryan.campbell Jun 2, 2006 2:49 PM (in response to starksm64)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.
http://tinyurl.com/p7jde -
63. Re: Breaking up common in jboss-head
ruel.loehr Jun 9, 2006 4:59 PM (in response to starksm64)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
cd common
./build.sh
To get the 4.0 branch version
svn co https://svn.jboss.org/repos/common/trunk/branches/Branch_4_0 common-4_0
cd common-4_0
./build.sh
I have published the artifacts which result from these builds to:
http://repository.jboss.com/jboss/common/
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) -
64. Re: Breaking up common in jboss-head
ryan.campbell Jun 12, 2006 7:01 PM (in response to starksm64)This looks ok to me.
We need to work out who has commit access.
Adrian
Dimitris
Scott
Alexey
Ruel
is this enough of a start? -
65. Re: Breaking up common in jboss-head
aloubyansky Jun 13, 2006 3:27 AM (in response to starksm64)Should be enough of a start.
WS and EJB3 guys sometimes modify JBossEntityResolver which is in the common. -
66. Re: Breaking up common in jboss-head
ruel.loehr Jun 22, 2006 4:30 PM (in response to starksm64)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.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCommonProject
The above wiki should answer your initial questions, but I am available to help you with any problems that may arise. -
67. Re: Breaking up common in jboss-head
aloubyansky Jun 24, 2006 5:14 AM (in response to starksm64)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).
-
68. Re: Breaking up common in jboss-head
starksm64 Jun 24, 2006 6:40 AM (in response to starksm64)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.
-
69. Re: Breaking up common in jboss-head
aloubyansky Jun 24, 2006 6:29 PM (in response to starksm64)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.
-
70. Re: Breaking up common in jboss-head
ruel.loehr Jun 26, 2006 9:40 AM (in response to starksm64)Alex, you should have commit rights as of Saturday. Please let me know if you are still encountering issues.
-
71. Re: Breaking up common in jboss-head
aloubyansky Jun 26, 2006 9:59 AM (in response to starksm64)Yes, I am.
-
72. Re: Breaking up common in jboss-head
ruel.loehr Jun 26, 2006 11:50 AM (in response to starksm64)TomBen found an issue which we have resolved. I worked with Alex and he is in good shape now as well.
-
73. Re: Breaking up common in jboss-head
ruel.loehr Aug 14, 2006 6:02 PM (in response to starksm64)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.
https://svn.jboss.org/repos/common/branches/logging_refactoring/
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.