Stephen Connolly wrote:
>
>
> On Mon, Jul 28, 2008 at 7:34 AM, Sahoo <Sahoo_at_sun.com
> <mailto:Sahoo_at_sun.com>> wrote:
>
> Stephen Connolly wrote:
>
> This is probably because some dependencies are being kept as
> -SNAPSHOT dependencies when they should not be, while other
> dependencies are not being kept as -SNAPSHOT dependencies when
> they should be.
>
> A quick rule of thumb is if the dependencies are within the
> same master pom & scm root, then they can all be -SNAPSHOT.
> If they are in different SCM roots, and there is no single
> pom.xml that will build them all then either they should be
> tied with non-SNAPSHOT versions or you will need to update
> them both and build them both repeatedly.
>
> What I tend to do when working on two or three trees in
> different SCMs in between releases is create a local pom that
> links all the separate SCM roots on my machine. That way I
> can keep the dependencies as -SNAPSHOT and work on the latest
> without having these build problems
>
> We plan to move to this model soon for components that are
> evolving together yet maintained in different SCMs.
>
>
> Sahoo,
>
> I know... I guess it's just I'd rather that people understand that the
> reason Maven seems to be causing glassfish lots of headaches is
> because of sub-optimal choices in how to use Maven not because of Maven.
+1.
Thanks,
Sahoo