Re: Three problems in beta and trunk - trunk fails out of the box currently

[Charles Severance]

Just some stories form Sakai. (1) We version all million lines of code and release *together*.  When we branch or tag for releases - we immediately update the version in the tag/branch so we keep from being confused as many develop on several branches at the same time. (2) To the extent we want to version independently - we made each major module a separate SVN tied together by a single externals file - that allows independent branching and tagging of each major component.  It is quite flexible and useful for a million lines of code - but not necessary here IMHO.  Using this approach makes svn update trickier and you can get in trouble - so I would avoid it until you *really* need it. /Chuck On Aug 30, 2006, at 8:17 AM, David H. DeWolf wrote: I think for now it's ok to release all together.  I don't see a problem with this.  As a matter of fact, we've never even discussed independent releases.  Commit Away! David David Elliot Metsger wrote: David H. DeWolf wrote: yup.  the maven resources plugin can help with filtering/replacement too. . . Ok so I've done what I proposed below in my working copy (I haven't committed it yet). One problem with my solution is that you cannot version the Pluto artifacts independently of each other.  I don't know if that is a problem or not. If that isn't a problem (or if it is a problem we can resolve later) I'll commit the patch, and of course feel free to change things around (you won't hurt my feelings) :-) Elliot