Yes, that works fine already. I've already used it for releasing Apache DeltaSpike where we do not have the pom directly under the root folder but in a ./deltaspike/ folder (in parallel to docs, etc)
LieGrue, strub >________________________________ > From: Olivier Lamy <ol...@apache.org> >To: Maven Developers List <dev@maven.apache.org> >Sent: Thursday, September 13, 2012 9:45 PM >Subject: Re: [VOTE] Move Maven projects sources to git > >2012/9/13 Mark Derricutt <m...@talios.com>: >> Whilst it "may work" it's also rather horrible, unless every module in said >> repository shares the same version number and gets released at the same time. >> >> If however it's planned to go this route of a single repository, but >> separate release cadences for modules, some rework and new releases of the >> maven-release-plugin should probably first be ironed out. > >That must work since 2.2 (see http://jira.codehaus.org/browse/MRELEASE-457 ) > >> >> >> >> >> On 12/09/2012, at 12:13 AM, Kristian Rosenvold >> <kristian.rosenv...@gmail.com> wrote: >> >>> Tagging the whole repo svn-style definitely works, and the >>> maven-plugins repo isn't that big either. We could consider stephen's >>> subdivision suggestion, but really I think it's totally viable to just >>> leave one big repo. We're talking 37mb for the full history of >>> everything, give or take a few bytes. Not too much by any modern >>> standard. >> > > > >-- >Olivier Lamy >Talend: http://coders.talend.com >http://twitter.com/olamy | http://linkedin.com/in/olamy > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
