(sorry for going on about this; its been a passion ever since some idiot (me) created 1.4-only jars of phoenix way back)
On Sun, Aug 20, 2006 at 04:54:58PM +0200, Jorg Heymans wrote: > On 20 Aug 2006, at 15:50, Leo Simons wrote: > >My main beef with maven 2 (corporate stuff) is its so hard to have > >"repeatable" builds, eg making sure I can take some source code a year > >from now and result in a build with exactly the same binaries, so I'd > >love to see you be very precise in keeping logs, perhaps even going so > >far as cleaning out ~/.m2, creating the builds, then zipping ~/.m2 and > >pushing it in SVN somewhere close to the release tag, then doing later > >release candidates with -offline. Or something; haven't fully > >figured it > >out yet. Does cocoon have a process? > > The release plugin will refuse to work if it detects any *-SNAPSHOT > dependencies in you pom. It's not an absolute guarantee to have a > repeatable build enviroment but it goes a long way already. Sorry, but not really. It goes about 60% (not even 80%). Maven's automatic magic plugin management gets in the way. Maven2 is what I would classify as "stable", but its not "mature" in the sense that ant or make are. Maven 1 is more mature than maven 2 precisely because no-one is working on it -- all the bugs are likely to stay in :). > If required i can tar up ~/.m2 ofcourse, no biggy - that should give you > the 100% reproduceability then. At cocoon we don't have a process in > place for this. I was afraid you'd say that. Jason told me the same thing a while ago. I think I'll go and harass them a bit more. Or maybe I'll write a howto. In any case, don't worry too much and just do the releases. I just resever the right to be grumpy ;) LSD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
