Granted, I also think it's a best practice to version JAR files; however, I'm not convinced that putting the version in the file name is a good idea, let alone a best practice.
Filenames don't seem to be a good place for storing data like this, especially when you have Sun's versioning specs (http://java.sun.com/j2se/1..3/docs/guide/versioning/spec/VersioningSpecification.html), which put version data in the manifest. But that's my take, and we've already been down that road before :-) I'm not sure why Steph doesn't want version info in the filenames, but maybe he and I are in the same boat: http://marc.theaimsgroup.com/?t=106727058800001&r=1&w=2 Based on that thread, I build the unversioned JARs, deploy them in my app server, and then rename before pushing them out to the repository. Kyle _____ Kyle Adams | Java Developer | Gordon Food Service | 616-717-6162 >>> [EMAIL PROTECTED] 12/12/03 11:05AM >>> All jars MUST have a version. It's a best practices. Emmanuel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
