Indeed, most usecases should use the release plugin. On top of that, however, we release a snapshot of our product on a nightly basis (via CC) and we want the snapshot's sources and javadocs to be released too, so that the developments can tinker and play with them and test them out (sort of like alpha releases, but on a regular basis). This helps us identify issues outside (and in addition to) the regular alpha/beta/rc/final release cycle. For such a usecase, we found that parameter very useful.
I admit usually one uses the release plugin to perform releases - which, btw, when built from the source code works beatifuly now! Any idea when a release will be out? :) Anyway - just my 2cents.. On 11/12/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > The release plugin specifies -DperformRelease internally, so it isn't > required on that page. > > - Brett > > Arik Kfir wrote: > > Hi, > > > > I think it might be a good idea to mention the "-DperformRelease=xxx" > > parameter in the > > http://maven.apache.org/guides/mini/guide-releasing.htmlpage ("Guide > > to Releasing") as it's quite useful. > > > > I, for one, did not know about it and had to manually bind the javadoc > and > > sources plugins in my POM before discovering it! :) > > > > Cheers, > > Arik. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
