>Also have a look at versions-maven-plugin
That's what I meant earlier, not dependency-maven-plugin. I haven't
personally used it yet, but I've shown it to several clients / trainees
and it's worked well for them in this case.
-
T
dules. Then when it's time to
> release you know all the other things you must release because they are set
> as snapshots.
>
> -Original Message-
> From: Zac Thompson [mailto:zac.thomp...@gmail.com]
> Sent: Friday, April 03, 2009 8:43 PM
> To: Maven Users
thomp...@gmail.com]
Sent: Friday, April 03, 2009 8:43 PM
To: Maven Users List
Subject: Re: Maven 2.0 project versions, dependency versions, and perpetual
releasing
I am willing to continue using snapshots during the dev cycle. I
don't seek to eliminate them completely, but they are getting in my
I am willing to continue using snapshots during the dev cycle. I
don't seek to eliminate them completely, but they are getting in my
way. It's not SNAPSHOT versions of the projects themselves that is
the obstacle, but SNAPSHOT dependencies.
My challenge is that the dev cycle for a slice of the s
Use snapshots during your dev cycle and publish your
non-developer-desktop builds as official releases. There is the
dependency-maven-plugin that can ease the updates of cross dependencies,
but if you structure your build tree effectively, this will be minimal.
You're on the right track, but don't
