On Tue, 2004-02-03 at 01:12, Ben Walding wrote:
> Jason wrote:
> 
> >They are never to be removed from the central repository.
> >
> >  
> >
> There are probably a couple of reasons that an artifact would be removed 
> / replaced in the repository
> 
> 1) Legal reasons, eg. we aren't allowed to distribute them (javamail, 
> ejb, ... damned Sun)

This there is just nothing we can do about.

> 2) Corrupt archives - no point in having something in the repository if 
> it is corrupt - fix it or remove it

Leave it, and the project does it again.

> 3) Trojanned archives - while I hope this never happens, we would fix / 
> remove archives that had been trojanned.  However if we can't work out 
> how it got trojanned, then that represents a whole other kettle of fish 
> in terms of validating the repository.

Sure, but this would certainly be an exceptional case.

> 
> Of course there is also some edge cases such as archives that have 
> security vulnerabilities. This could be handled by artifact metadata 
> that warned clients that the archive had issues.

Have any examples? 

> I'm also wary about the proliferation of shitty snapshots everywhere.  

Eventually as practices become standard there will be less cruft but the
cruft will stay there for all to see.

> This is less a problem in ibiblio at the moment as uploads are manual 
> and hence limited. Once an automated way of pushing snapshots into the 
> repository becomes widely spread, then we could have an explosion of 
> snapshots that really don't have any value (I realise that some 
> snapshots do have value, but for the most part they probably wouldn't 
> have long term value)  Flagging artifacts as transient and then warning 
> about them in build tools might be a general solution to this.

Possibly but don't really know what people have used along the way for
releases. At some point in the future we may have something that could
determine with relative certainty that an artifact was not part of any
release this will be a some time in coming and until then, given
ibiblios's resources, that there's no downside in keeping the artifacts
around except for the rare cases where concerns of security override
those of archiving for historical intactness.

> sd
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to