Hi there, I do not think there is any real benefit in the addition of this field. The prepare goal in the maven-release plugin is all about tagging a working instance of the project within the SCM.
The plugin ensures you are in sync with the development trunk of the project. Next by executing the build life cycle on the trunk maven is ensuring that at least you can fully compile and pass the unit tests. If someone used this flag and bypassed this stage in the prepare process a tagged instance of the project could get into a state where it may not even compile. Maven at this stage is helping you to make sure the SCM is in the best possible state, (it can build). If a release is performed, (extracted based of a tag name) and it cannot even compile then that release is worthless and a waste of resources preparing it and storing it in the SCM. It is all about not wasting time at later stages. If you take the hit and ensure the release can complete the full build life cycle then developers can spend time later addressing the real issues and not the basics of whether the release can be built in the first place. Also the release process could be divided between 2 people, someone to prepare the release and another to perform it. By completing the build life cycle both parties can enough that they are delivering a working solution to their audiences. Hope this is cool, just want to explore the issue. Trent On 23/11/05, dan tran <[EMAIL PROTECTED]> wrote: > Hello, At my shop, we do daily realease using maven-release-plugin. > Currently maven makesure the source is buildable before perform the label. > Then at the perform step, maven builds again. > > Is it reasonable to have maven skips the build at prepare step. > This way we can cut down the build time ( in half) ? > > We can introduce a doPrepareBuild field which defaults to true. > > -D > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
