I'd prefer to use the alternative he mentions in the email, uniquely identify all JARs including the dev JARs (perhaps with a timestamp). If I were maintaining a project, I want full control of when I chose to change a dependency, not when someone else decides to load a new jar in the central repository. This is why I'd prefer to uniquely identify all of the JARs.
On Tue, May 07, 2002 at 10:06:45AM -0400, Kurt Schrader wrote: > As Jason mentioned below, I think that we need to restore update-jars > in Maven for the time being. Here's my +1 to me doing so. I'll put > it back in unless someone has a problem or a better solution. > > ---------- Forwarded message ---------- > Date: 29 Apr 2002 12:12:35 -0400 > From: Jason van Zyl <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: A few thoughts > > o Restoring update-jars or cleaning up the naming of the JAR files. I > removed update-jars and replaced it with an automated update facility > but it won't work for JARs that don't have a differentiating name. This > is all part of the theory that all JARs should be uniquely identified > even if it is a CVS dev snapshot. And the differentiation has to be at > the resource level or the JAR not the storage level like CVS. I don't > want to have to rely on the storage mechanism for versioning. Anyway > either someone can restore the update-jars or do the grand JAR renaming. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
