On Nov 6, 2006, at 9:09 AM, Matt Hogstrom wrote:
As far as 2.0 goes it sounds like there is work in progress here
and it seems to make sense to define a home for this work. I
expect that server/trunk would be destabilizing to the release Dain
and Alan are working on as it involves Java 1.5 and newer spec
levels. Sandbox has worked so far but I think it would help people
understand the process of we had a place to start incorporating
Java EE 5.0 and they could grab it and build it. I think a
location in server/branches/javaee5 makes sense as a rallying point.
What do other people think about bringing this the Java EE 5.0
story together in that location? We could follow David's existing
methodology in sandbox where we build trunk and have an incremental
build on top of that in branches/javaee5 and it would be visibile
to others that wanted to start getting involved. Thoughts?
I think this is a bad idea: it breaks the model that anything in
server/** is a complete server and provides no advantage I can see to
working in the sandbox. I am strongly against this.
I would much prefer that we develop each jee5 feature as a plugin and
put each one -- modules and configs -- into a plugin in a (new)
plugins area. Then we can move each current trunk feature into the
plugins area one by one and actually get an improved organization.
We could base assembly on the micro-g or have a separate jee5
assembly area.
thanks
david jencks
Matt Hogstrom
[EMAIL PROTECTED]
