> And why you don't want to use this structure ?. I guess the main argument is that eclipse cannot nest projects, so there's no way to edit your parent pom (+ parent site, etc) with eclipse (instead you have to vi + svn commit on the command line).
BUT: My gut feeling tells me that this is no maven-scm problem but a problem within the maven-release-plugin. Can anyone shed a light on this? So I agree with Chris that we should address this issue, but also with Olivier that this should not hinder us from releasing maven-scm. LieGrue, strub --- Olivier Lamy <[EMAIL PROTECTED]> schrieb am Mo, 25.8.2008: > Von: Olivier Lamy <[EMAIL PROTECTED]> > Betreff: Why using flattened structure [was Re: [VOTE] Release Maven Scm 1.1 > (take 3)] > An: scm-dev@maven.apache.org > Datum: Montag, 25. August 2008, 10:29 > I change the subject because I don't see any link with > the vote on the > scm release. > > And why you don't want to use this structure ?. > > -- > Olivier > > 2008/8/25 ChrisGWarp <[EMAIL PROTECTED]>: > > > > > > > > Olivier Lamy wrote: > >> > >> Try : > >> svn co > >> > http://svn.warpspeed.com.au/test-repos/FireDragon/branches/olamy-test/ > >> FireDragon-olamy-test && cd > FireDragon-olamy-test && mvn > >> release:prepare release:perform -B > >> > >> I have build two releases with success here : > >> > http://svn.warpspeed.com.au/test-repos/FireDragon/tags/ > >> > > > > You have the results that I would expect from the > normal nested maven > > approach. > > > > However, it totally ignores my situation, namely the > flattened structure, > > which is what I need to have working. > > > > -Chris > > > > -- > > View this message in context: > http://www.nabble.com/-VOTE--Release-Maven-Scm-1.1-%28take-3%29-tp19123852p19139773.html > > Sent from the Maven - SCM mailing list archive at > Nabble.com. > > > > __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
