I'm all for version numbers in JARs, but we also need scripts that add (e.g.) all JARs in a given dir to the classpath, rather than list them. If we list them explicitly, we have to change those scripts when we change the JAR name. Manik Surtani wrote: > I was trying it out as per our discussions on dev. > > Also, I think it is best to have version numbers on such jars just > so we're clear on what versions we're using (I couldn't tell which > version of JCL we had before, for example) > > What does everyone think about version numbers in the jars we use, > like this? > > Cheers, > -- > Manik Surtani > > Lead, JBoss Cache > JBoss, a division of Red Hat > > Email: manik(a)jboss.org > Telephone: +44 7786 702 706 > MSN: manik(a)surtani.org > Yahoo/AIM/Skype: maniksurtani > > > On 11 Sep 2006, at 18:29, Brian Stansberry wrote: > >> Hey dude, >> >> Looks like you checked in commons-logging-1.1.jar and >> log4j-1.2.13.jar. >> Was this intentional? These files have a different name from >> what's in >> the Eclipse project classpath, so that breaks Eclipse. I can >> check in a >> fixed Eclipse .classpath file, but don't want to if you're going to >> revert the library change. >> >> Brian Stansberry >> Lead, AS Clustering >> JBoss, a division of Red Hat > > _______________________________________________ > jbosscache-dev mailing list > jbosscache-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosscache-dev > -- Bela Ban Lead JGroups / Manager JBoss Clustering Group JBoss - a division of Red Hat