On 23 Aug 2006, at 12:11, Leo Simons wrote:
(sorry for going on about this; its been a passion ever since some
idiot
(me) created 1.4-only jars of phoenix way back)
no worries, this needs to be discussed as it's obviously important to
more people.
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
mmmm so what if i tar up the maven version used as well ?
I'm not that familiar with maven's automagic plugin management, can
you expand a bit more how this could be problematic ?
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 :).
yep.
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 ;)
ok that's cool Leo. Thanks for your input.
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
