On Tue, 2004-02-03 at 08:46, Jeffrey D. Brekke wrote: > >>>>> On Tue, 03 Feb 2004 01:21:01 -0500, Jason van Zyl <[EMAIL PROTECTED]> said: > [SNIPPED] > > >> 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. > > [SNIPPED] > > I always took the idea of using a SNAPSHOT of anything as a temporary > dependency that could be removed once a release is put forth. In > otherwords, use SNAPSHOT's, but don't release with them.
Right, that's the symlinked SNAPSHOT which is attached to a real timestamped artifact. Those are the things that won't be removed, I wasn't clear. > For releases, even alpha/beta/rc, they should remain. I guess I > didn't know about leaving all SNAPSHOT's around though. The actual foo-SNAPSHOT.jar gets relinked all the time, it's the actual timestamped version that it refers to that doesn't get erased. > I guess we're > at the mercy of projects that never release anything but SNAPSHOT's in > which case, any artifact that is put in the repo is *released*. When the SNAPSHOT is released, it is really a timestamped version. Just releasing foo-SNAPSHOT.jar is evil, bad and will have to be prevented using tools if that's what's happening. Using the plugins to release a snapshot is made by created a timestamped version of the JAR and then on the server a symlink (or on windows a copy) is created between the real artifact and the SNAPSHOT. Without deploying a SNAPSHOT the correct way there is no mapping between the two which means the release plugin cannot resolve SNAPSHOT names in your POM to real timestamped versions of the artifacts. -- 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]
