How to Prevent Redeployment of an Artifact?

[Hilco Wijbenga <hi...@gmail.com>]

Hi all,

I'm in the process of setting up a Maven environment. Things are
working nicely but I noticed that I could repeatedly deploy the same
artifact (i.e. with the same version). For snapshots that's no problem
but for releases that's not what one wants.

I couldn't find anything in the POM description that would prevent
this. Google also didn't provide any answers. So how does one prevent
redeploying artifacts? The only thing that I could come up with was
running a cron job that would set everything (excluding
maven-metadata.xml*) to read-only.

Is there a best practice for this?

Cheers,
Hilco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: How to Prevent Redeployment of an Artifact?

[Dan Tran <da...@gmail.com>]

you should group your project into logical modules and release the
groups as often as you like, however i dont think it is wise to let
everyone do the release at will, there should be a release manager to
do that job.  Take a look at maven continuum 1.1 which can automate
the release job for you in a control manner.

also take a look at maven itself which has multiple project groups (
ie , plexus core, plexus-utils, plexus archiver, doxia, scm, maven
etc)

hope it helps.

-D



On 8/27/07, Hilco Wijbenga <hi...@gmail.com> wrote:
> On 8/27/07, Dan Tran <da...@gmail.com> wrote:
> > you should use maven-release-plugin to do the deployment. This plugin
> > always increment the release version after it releases the artitfacts.
>
> I will definitely take advantage of maven-release-plugin. So far I've
> been using "mvn deploy" as these are just tiny modules (and I'm just
> trying things). I have also assumed that in a more Agile environment
> everybody should be able to do releases of these modules (not of the
> entire app).
>
> Do you think releasing (even of underlying modules) should always be
> done by a select few?
>
> We're just starting on the road to Maven bliss so I'm trying to figure
> out what countless people have already mastered. :-) I've been looking
> for the philosophy behind Maven releases but I haven't found much.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: How to Prevent Redeployment of an Artifact?

[Hilco Wijbenga <hi...@gmail.com>]

On 8/27/07, Dan Tran <da...@gmail.com> wrote:
> you should use maven-release-plugin to do the deployment. This plugin
> always increment the release version after it releases the artitfacts.

I will definitely take advantage of maven-release-plugin. So far I've
been using "mvn deploy" as these are just tiny modules (and I'm just
trying things). I have also assumed that in a more Agile environment
everybody should be able to do releases of these modules (not of the
entire app).

Do you think releasing (even of underlying modules) should always be
done by a select few?

We're just starting on the road to Maven bliss so I'm trying to figure
out what countless people have already mastered. :-) I've been looking
for the philosophy behind Maven releases but I haven't found much.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: How to Prevent Redeployment of an Artifact?

[Dan Tran <da...@gmail.com>]

you should use maven-release-plugin to do the deployment. This plugin
always increment the release version after it releases the artitfacts

-D

On 8/27/07, Hilco Wijbenga <hi...@gmail.com> wrote:
> Hi all,
>
> I'm in the process of setting up a Maven environment. Things are
> working nicely but I noticed that I could repeatedly deploy the same
> artifact (i.e. with the same version). For snapshots that's no problem
> but for releases that's not what one wants.
>
> I couldn't find anything in the POM description that would prevent
> this. Google also didn't provide any answers. So how does one prevent
> redeploying artifacts? The only thing that I could come up with was
> running a cron job that would set everything (excluding
> maven-metadata.xml*) to read-only.
>
> Is there a best practice for this?
>
> Cheers,
> Hilco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org