Re: Remove auto-resolution of plugin versions from Maven 2.1

[Matt Ryall]

On Jan 1, 2008 1:28 AM, Brett Porter <[EMAIL PROTECTED]> wrote:

> FWIW, This is precisely the functionality that the
> "generateReleasePoms" flag of the release plugin was intended to
> provide.
>

"Intended to provide"? Does it actually provide it?

The documentation for this flag seems a bit inconsistent. It's listed as a
property for 'release:prepare' at [1], but the example uses
'release:perform' [2]. Will the perform always use the release-pom.xml if it
exists?

Cheers,
Matt

[1] http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html
[2]
http://maven.apache.org/plugins/maven-release-plugin/examples/generate-release-poms.html

Re: Modifying deploy plugin to prevent deployment of existing versions

[Matt Ryall]

Hi Jason,

This sounds like a really great idea.

Is there an issue or wiki page I can refer people to with regard to this
change? Seems like it should be an improvement noted on the deploy plugin
JIRA.

Cheers,
Matt

On 10/19/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> I've been working on some release/deployment tools lately for a
> client and I modified their deployments so that you could not
> accidentally release the same version of an artifact more then once.
> I can stop this on the server side only when running a repository
> manager, but we have some simple Apache servers that are DAV enables
> and someone release an artifact with the same version by mistake and
> wreaked havoc for 4 hours.
>
> I think this one is pretty obvious, I'm not going to write a proposal
> I'm just going to fix it because it's not very bright that we allow
> the re-release of something that already has been. I'll leave a
> option to redeploy if you so choose in the event the driver knows
> what he's doing.
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> jason at sonatype dot com
> --
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>