maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Hübner" <sthueb...@googlemail.com>
Subject Re: Project structure and releasing
Date Sat, 01 Jul 2006 09:29:48 GMT
Andy,

are you saying, that deploying the multiproject-pom as 1.2.1 would
automatically update the submodule's dependency on their parent from
1.2-SNAPSHOT to 1.2.1? Is it even necessary to declare the parent's
version the submodules refer to?

-Stefan

2006/7/1, Andrew Williams <andy@handyande.co.uk>:
> I may be wrong, but if your parent is, as in the book, a pom packaged
> artifact with a module list then doing a release at that level should
> prompt (with sensible defaults) the release of all the modules.
>
> Andy
>
> On Fri, 2006-06-30 at 21:29 +0200, Martijn Dashorst wrote:
> > All,
> >
> > I've updated the structure of my projects that depend on one another
> > to the structure as proposed in the better builds with maven book.
> >
> > The one problem I have with this way of building is the link to the
> > parent project:
> >
> > <parent>
> >     <groupId>wicket</groupId>
> >     <artifactId>wicket-parent</artifactId>
> >     <version>1.2-SNAPSHOT</version>
> > </parent>
> >
> > Now I have to update all projects to perform a release of say version
> > 1.2.1. Or is there a better way?
> >
> > BTW. All projects use snapshot dependencies as adviced earlier on this
> > mailinglist.
> >
> > 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


Mime
View raw message