2011/2/20 Ondřej Světlík <[email protected]> > Dne 19.2.2011 20:58, Wayne Fay napsal(a): > > <uniqueVersion>false</uniqueVersion> >>> >> >> Let me guess -- you're using Maven 3, right? >> >> From the Maven 3 compatibility notes: >> Non-unique Snapshot Deployments >> The setting<uniqueVersion>false</uniqueVersion> for a distribution >> repository has no effect in version 3.x, snapshot artifacts will >> always be deployed using a timestamped version. >> >> >> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments >> >> Wayne >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > You're a genius. Thanks :-). One mystery solved. > > If this is an internal company repository, then put a repository manager in front of it.
Nexus can manage the explosion of snapshots by settings policies - i.e. only keep the latest one, when the artifact gets released then delete any snapshots, only keep snapshots for a certain time. I'm fairly sure Archiva has similar features for managing this.
