I don't think that 1.5 development will result in new releases...
those will all be SNAPSHOT artifacts anyways.
Just some questions about this strategy...
Which modules go where? Will each of these trees have a single
version? How will the overlap between J2EE 1.5 and 1.4 fit? Where
will common config go?
--jason
On Oct 2, 2006, at 11:55 AM, Dain Sundstrom wrote:
How about we split them into j2ee 1.4, j2ee 1.5 and independent
modules for the non j2ee specs? This will prevent the flux from
the 1.5 development from causing lots of new versions for the 1.4
specs.
Just another middle ground idea. Thoughts?
-dain
On Oct 2, 2006, at 11:16 AM, David Blevins wrote:
On Oct 1, 2006, at 4:31 PM, David Jencks wrote:
In any case PLEASE think about this and make your opinion known
soon.
If we could at least make a compromise that'd be very great, all
or nothing is not the only way.
Maybe we could just remove these core specs from trunk or
something (we have several tags):
ejb
servlet
jsp
jms
transaction
connector
qname
If all the rest became "one version number" specs released at the
pace of the most changing spec, that'd still be less desirable but
be at least better.
Maybe not the best idea, just trying to find some middle ground.
Thoughts?
-David
