[Opensource] Re: [Expresso CVS:Commits 5.3] *** Important Commit ***

[Michael Rimov]

At 09:49 PM 8/1/2003 +0100, you wrote:
>One thing that I would like to change is to actually rename the
>important struts 1.1 JAR files. So that we get the version number of the
>distribution in the filename.
>
>commons-beanutils.jar   =>      commons-beanutils-1.1fcs.jar
>commons-collections.jar =>      commons-collections-1.1fcs.jar
>
>..
>
>struts.jar              =>      struts-1.1fcs.jar
>
>Is this a good idea?
>
>Or we can use the actual jakarta version numbers. Is this a good idea?


#1 - I'm using the actual jakarta version numbers.  Folks seem to like that 
they could identify the component.  That way, issue-wise, they can track 
whatever they need through the jakarta site rather than having to provide 
additional version information.

#2 - Personally, I'm against having the version numbers in the file names 
because I've spent more than one debugging session trying to track down 
some really odd behavior to only find out that it was due to failing to 
remove the old version so I had, for example, log4j1.2.8 and log4j1.2.7 
both in the same directory when I copied in the updates.

I prefer using the jar file manifests for versioning whenever possible.  In 
fact, I've been submitting as bugs any incorrect version numbers in the 
manifests to the respective apache projects.  You might want to do the same 
if you come across some particulars that don't have it set up.

As an aside, you can quickly check the package version number by going to 
the Status controller. [Application -> Things That Are Happening 
Now]  There is a new tab for 'Installed Packages' that allows you to browse 
through everything and installed and displays version information as 
defined by the jar manifests.

For the .war and LE-war distributions, the classes are jarred with the 
appropriate version information in the manifests as well.

                                                         -Mike