Ted Husted wrote:
So let's go with this then:
* The Struts Core Library distribution can start out at 1.3_00, and
not increment again until all of its components are GA. When the
Struts Core subproject increments a major or minor number, then the
Library distribution will follow suit.
* When the new subprojects (Scripting, Flow, Faces) are found to be
compatible with Struts Core 1.3.0 (or later), their release numbers
will increment to 1.3.0, same as the dwarves.
I'd like Scripting and Flow to not automatically be 1.3.0 for several reasons:
1. It implies they are at the 1.3 stage in their development, which they
certainly are not as they haven't seen a 1.0 release yet. Flow, in particular,
is more experimental and probably won't see a 1.0 for a little while.
2. These subprojects might be targeting older versions of Struts as they may
have their own user base. For example, BSF is targeting 1.1 or later, even if
it works correctly with Struts Core 1.3.0. The 1.3.0 designation on it might
throw users off.
Actually, I think both points are relevant for Faces as well. BTW, was "Struts
Distribution" voted down already, because I thought that was the most intuitive
name for what we are trying to do.
Don
* I've been enumerating the contents as the zips for each subproject.
That approach would include a ton of redundant binaries. Perhaps it
would be better to go back to the 1.2.x Library idea and make this a
distribution of JARs (including external dependencies). If people want
to install the source or documentation or such locally, they can
download the individual subproject releases.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
