Hello, I have a version of the contrib/jetty module (from the
jboss_buildmagic) branch, which has been updated to function with the new
build system. It looks like you work with most of the jboss-jetty releases,
so I wanted to pass this by you before I commit anything back to HEAD.
As the changes stand now (in the jboss_buildmagic) branch, the plugins/jetty
module can be included in the jboss-all supermodule. When a release is
built it will compile the support classes into jetty-plugin.jar and copy
over all of the jetty support jars into lib/ext.
There are a few issues that I wanted to touch on here.
First, I added the Jetty 3.1 rc7 & Jetty3Extra v0.0.5 (which I just
downloaded from SF) into thirdparty/mortbay/... This is the first issue,
that currently there is no way to allow per module thirdparty libraries to
be included selectivly. It is possible to trim down the stuff from
thirdparty, but then when items are added, users are forced to `cvs
checkout` of that module to use the newest CVSROOT/modules defintions.
The Jetty support jars are small, so for now I just added them. I would
like to have a general solution to this problem though. It might be
including per module specific jars in a local lib directory, or it might be
defining thirdparty includes for each module, which would mean that each
module would have copies of each jar that it depeneds on, but there would
really be only one version in the repository. Not sure what is best at the
moment.
Second, I think that it would make life easier for releasing the jboss-jetty
distribution, but setting up a new jboss-jetty module, which would compile
and create the proper jboss-jetty-xxx.zip. This is currently possible, as
was done for the standalone JBossMQ, but there are some minor problems.
One is that since modules "export" files into a rather static namespace, it
is mostly an all or nothing when it comes to including released files from a
module into a project release.
I plan to have this fixed. I am thinking about a few ways which this could
be implemented, but I will probably not have time to actually implement this
for a little while.
Third, there is no really easy way to add custom plugin configuration to the
bits generated by the jboss/server module. I hope that once RH is ready
that this can be done by simply installing a .sar and a .jcml-configlet into
a deploy/service/ directory or something.
Any ways, I would like to merge the changes from jboss_buildmagic for the
plugins/jetty (contrib/jetty) module, so that things do not get out of date.
What do you think?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
