This is independent of another question, which we should also probably discuss, which is how we version non-core artifacts. I generally prefer sharing version numbers -- I find the J2EE methodology of rolling in a number of disparate version numbers into a single release continually confusing, although I think that Ted has suggested it as the approach for future Struts releases once we have our pieces all broken out. I know that if we want things to have their own release cycle, then we may not simply be able to share the major "Struts version number", but like I said, I'm not real fond of the only other alternative I have thought of.
I admit to having no solid proposal for either of these things.
For between-release artifacts, I have seen someone use "SNAPSHOT" in a version name, which I would recommend against, as Maven always tries to download dependencies which contain that string, something which quickly becomes tiresome. I would prefer that we not use real version numbers in the project.xml file until the moment when a release is being cut, to avoid confusion.
In my uncommitted work on the ActionContext, I am using "struts-1.3.0-dev". I think using the expected next release number plus "-dev" is a decent compromise, but I'm happy to hear other ideas.
Joe
At 5:46 PM +0000 1/19/05, [EMAIL PROTECTED] wrote:
Author: jmitchell Date: Wed Jan 19 09:46:35 2005 New Revision: 125632
URL: http://svn.apache.org/viewcvs?view=rev&rev=125632 Log: el now builds a good distribution (well, with maven anyway) Modified: struts/el/trunk/project.xml
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
