On 10/29/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > I doubt that given my visitation of production environments. But that > said the portion from our own POM provides the same functionality, or > it would even be preferable in subsequent versions of the release > plugin to make these goals default. The problem therein is selecting > the right version. Ultimately any sane group of developers wants to > see this information in their face. What is being used to produce the > release and what version of any tools/plugins being used.
Of course explicit configuration is better, but it's been in the super pom for a long time now. I think all Brett is asking is "How are we going to help people transition from 2.0 to 2.1?" I agree that the release profile shouldn't be in the super pom, but having it just disappear will be a shock. Is there any way to "deprecate" this behavior in 2.0, maybe by printing a message when the release profile is activated? I'm happily using the Continuum release functionality (but I think it's the same code) and have used the release plugin for an Archiva release. It works fine. (Yes, with Subversion.) Are the issues you mentioned with Perforce and Clearcase entered in JIRA? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
