Despite a few minor problems, I have the server running after having all of
its components built from sources. I am running the testsuite againt it
right now, and hopefully it will fail only on the jmsra tests, which a
server built from jboss did as well.
There are still a few more things left to be done, most notibly the
migration of the testsuite. I had to use the current jbosstest module to
validate the new server build, because I have only just started to deal with
the subprojects and junit tasks from the testsuite.
I am sure there are still a few more kinks left in the system, though I
expect they will be build related like the problems you can with build.sh.
This is a problem that I knew I would run into, especially with win32 users.
On that note, I did test a build the other day on win32 using both cygwin
and the standard cmd prompt. The major thing here is that I am no .bat/.cmd
wizard and such I can not really produce the proper win32 script to replace
build.sh; perhaps that is not even possible. One easy work around is to
check out the 'buildmagic' module and add buildmagic\bin to your path and
run 'ant'. This works fine. Perhaps someone more familar with win32 could
write a simple .bat .cmd or small .exe or .com which would do what build.sh
does. The major function of build.sh is to try and locate the
buildmagic/ant install for the current project and use it, since it has all
of the proper xml parsers and extention tasks required to make everything
work.
I am not really sure how you, marc and the team want to move forward on
this. I would guess that there is still a few more days of work to get the
testsuite upto speed, forgetting the manual at the moment all together (I
don't think I could get the current module to build any docs).
I am convinced that this build system will make life much easier on
developers and release engineers. I did my best to clean up the build
files, standardize the targets, task usage and property names, but it was
not easy...
There might be a few minor, minor problems with the server generated by this
build system, but I would suggest updating HEAD with it sooner than later
(assuming that is what is desired that is). This is mostly so that I don't
get caught in an endless loop of integration work for keeping the branch up
todate, as well as allowing other developers to help ensure that the new
system is doing the right thing.
The projects that I work on (and get paid for) are based on JBoss, so I am
dedicated to ensuring that the build system will work, though I need to get
back to actually writting code that will run inside of it, instead of build
it.
* * *
Here is a summary of the issues that I can think of at the moment:
jboss/server
o src/test/** is not being compiled because it is using out of date
package names.
o the hypersonic, instantdb, castorjdo and tyrex support have been
moved to plugins/varia.
o jsr77.jar is still living in src/lib
jboss/admin
o had to update ejbdoclet usage to 1.2, and the generated jar files
probably need to include the correct deployment descriptors generated
by it.
jboss/testsuite
o need to update the build files for each build-*
o need to hookup the junit tests from run_tests.xml into the tests
target
jboss/security
o not currently compiling org.jboss.test.* as it has some dependency
on hsql. I did not look into it further.
jboss/cluster
o not compling org.jbossmx.cluster.watchdog.* as it looks like it needs
an old parser. I did not look into it further.
jboss/manual
o does not actually do anything at the moment, I still can't get
style or fop to complete generation of anything.
jboss/plugins/jetty
o included in the jboss-all module, but not currently hooked up to the
build system. Ignore for now.
jboss/plugins/varia
o not compling the tyrex plugin, the current source references classes
from jts that I can't find in the jar from sun and makes some api
calls to methods that do not exists. Probably also needs to be updated
for the current tyrex jar that is checked in. I think these are all
minor, but for now I left them as is and uncompiled.
buildsystem
o no build.bat in each module to provide build.sh functionality
* * *
I encurage anyone who is interested to try it:
cvs -z3 get -r jboss_buildmagic jboss-all
cd jboss-all/build
# this just sets up the local.properties file for each module
# you can omit this, but the first time you build you will end up with
# a jboss-2.5alpha-2001xxxxxx/ directory instead of DEV
./build.sh configure
# this will build the full server but assume that javadocs are already
# generated and thus you won't get them. I suggest this for the first
# time, because it is faster. Edit local.properties to turn it off for
# good.
./build.sh -Djavadoc-generated-already=true
# at this point you should have a built server
cd output/jboss-2.5alpha-DEV/bin
./run.sh
Let me know if there are any problems so I can fix them right away.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
