-1

All, please consider the impact such a change would have before casting your 
vote. You will now be responsible for manually updating dependencies as new 
versions are released. You won't simply be able to drop in new JARs and be off 
and running. This isn't as much of an issue for server-based development, where 
Tomcat (or some such) will automatically load JARs from your lib directory; in 
client-side deployment, you will be required to update your classpath in all of 
your build and deployment environments.

Other things to consider:

- As Todd mentioned, .NET does not include version numbers in DLL names; it 
uses the Global Assembly Cache (a sort of meta-directory for code) to partition 
versions
- Maven employs a directory structure to partition versions
- Mac OSX employs a directory structure to partition versions
- Other Apache projects including Tomcat and Ant do not embed version numbers 
in their JAR file names, only the distribution artifacts
- The JAR files will still contain the version information in the manifest

G
 
On Friday, March 27, 2009, at 11:07AM, "Christopher Brind" 
<[email protected]> wrote:
>+1
>
>2009/3/27 Todd Volkert <[email protected]>
>
>> There is some disagreement among the PPMC members as to whether we
>> should include version numbers in our JAR files that we release, so
>> I'd like to call for a consensus vote:
>>
>> Please cast your vote:
>>   [+1] include version numbers
>>   [=0] don't care
>>   [-1] don't include version numbers
>>
>> For some background, here are some links that discuss this issue:
>>
>> http://stackoverflow.com/questions/119426/jar-file-naming-conventions
>> - advocates embedding the version number
>>
>>
>> http://javahowto.blogspot.com/2006/05/java-jar-file-naming-conventions-and.html
>> - advocates embedding the version number unless the JAR is distributed
>> in a larger deliverable
>>
>> http://publib.boulder.ibm.com/wasce/V2.1.0/en/adding-java-libraries.html
>> - advocates using a directory structure to partition JARs
>>
>> ** note that .NET does not embed version numbers in the file name.
>>
>> Thanks!
>> -T
>>
>

Reply via email to