M2 transitive dependencies and releasing with M1

[Martijn Dashorst <ma...@topicus.nl>]

All,

I'm currently releasing Wicket and we have 2 projects: wicket and 
wicket-extensions. The extensions project has a dependency on wicket.

When I create a new version of wicket, do I need to release a new, 
updated version of extensions as well?

Or is this automatically resolved with m2?

Martijn

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: M2 transitive dependencies and releasing with M1

[Brett Porter <br...@gmail.com>]

The way it works is that a version you give becomes a "suggestion" to
m2, and depending on your conflict resolution strategy that version
might be selected, or the latest release.

We're still working on this, so we'll have it all set up by beta-1 to
test fully and will get some docs together. Currently, the m1 -> m2
conversion won't accommodate ranges (we'd need to let you add a new
property to your m1 pom).

- Brett

On 8/23/05, Martijn Dashorst <ma...@topicus.nl> wrote:
> All,
> 
> I'm currently releasing Wicket and we have 2 projects: wicket and
> wicket-extensions. The extensions project has a dependency on wicket.
> 
> When I create a new version of wicket, do I need to release a new,
> updated version of extensions as well?
> 
> Or is this automatically resolved with m2?
> 
> Martijn
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org