[news.eclipse.tools.jdt] Re: Which Eclipse project files to be placed un

[Eric Rizzo <eclipse-bugs@xxxxxxxxxxxx>]

On 9/17/09 2:35 PM, Michael Ludwig wrote:
> Eric,
>
> you've made me reconsider the issue. What I had in mind were JARs
> including the version number, like:
>
> xom-1.2.1.jar
> xom-1.2.2.jar
> log4j-1.2.15.jar

I usually do this, too, even when checking in the JARs. It just makes it 
easy to always know exactly what version is being used.
Note that when using User Libraries (ULs) or Classpath Variables (CVs), 
including version numbers in JARs doesn't really help. You could name 
the ULs or CVs to include version numbers, I guess. But I find it 
simpler to just check in JARs as I've described. Even though ULs and CVs 
are an option, they still require an extra manual step when setting up a 
new workspace, whereas checking in with the project adds no additional 
steps.

Glad to have helped,
Eric


> With those, the version is in the filename - so there does not seem to
> be any point in versioning the file. Of course, Joe Evil could rename
> the file - but he really shouldn't.
>
> (Okay, in order for this to be safe, there should be something in the
> build mechanism that ensures the JAR file is there with the correct
> version to prevent the build from succeeding with another version.)
>
> On the other hand, it's true that many JARs are not distributed with a
> version number or only with a partial version number:
>
> saxon9.jar
> xercesImpl.jar
> xalan.jar
>
> For those, there has to be some sort of versioning. Joe Evil would
> probably rename them, but I'll hitherforth consider putting them under
> version control.
>
> Thanks for your thoughts.