You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Jukka Zitting <ju...@gmail.com> on 2008/05/22 13:13:35 UTC

Timestamped snapshot artifacts in m2-snapshot-repository

Hi,

Is there some guidance on whether snapshot artifacts deployed to
m2-snapshot-repository should have unique version timestamps instead
of the -SNAPSHOT label?

If unique versions are better, how should a project avoid excessive
disk usage over time?

BR,

Jukka Zitting

Re: Timestamped snapshot artifacts in m2-snapshot-repository

Posted by Brett Porter <br...@apache.org>.
On 22/05/2008, at 9:13 PM, Jukka Zitting wrote:

> Hi,
>
> Is there some guidance on whether snapshot artifacts deployed to
> m2-snapshot-repository should have unique version timestamps instead
> of the -SNAPSHOT label?

It's really up to you and your needs. I prefer timestamped ones  
overall, as long as they are properly maintained.

>
>
> If unique versions are better, how should a project avoid excessive
> disk usage over time?

At present, each should be mindful of this themselves (eg, delete  
snapshots once a version is released). This is particularly a concern  
if you are deploying from CI and so generating large numbers.

Cheers,
- Brett

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


Re: Timestamped snapshot artifacts in m2-snapshot-repository

Posted by Steve Loughran <st...@gmail.com>.
On Thu, May 22, 2008 at 12:13 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Hi,
>
> Is there some guidance on whether snapshot artifacts deployed to
> m2-snapshot-repository should have unique version timestamps instead
> of the -SNAPSHOT label?

On this subject, where do I scp stuff to get it in there? Hadoop wants
to put their artifacts up, and I'll need to sneak in a snapshot copy
of commons-cli-2.0 to go with it,

>
> If unique versions are better, how should a project avoid excessive
> disk usage over time?

CI servers are trouble; they can builds lots a day. Maybe the update
rate should be reduced to something more laid back, like weekly
updates. That should be infrequent enough you could keep them there up
until the next full release comes out, at which point you could delete
them all -so as to force users to pick up your new release.

-steve