As far as distribution size (for releases), I suppose we could take
an approach where we package the dependencies under a separate folder
(similar to what Spring and JSF RI do), and provide a build.bat and
build.sh file that can assemble it on the other end.
--
James Mitchell
678.910.8017
On Nov 3, 2005, at 6:06 PM, 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'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]
