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)
2) Corrupt archives - no point in having something in the repository if it is corrupt - fix it or remove it
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.
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.
I'm also wary about the proliferation of shitty snapshots everywhere. 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.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
