Re: Checkout-related issues

Hi,

Greg Irvine wrote:

>So if you have dependencies on external jars etc, you all have to
>manually set up the specific dependencies EVERY time you check out a
>project? Yuck!
>
>As an FYI:
>Here we check in the .project and .classpath files. If we have any
>dependencies on other jar files we use CLASSPATH VARIABLES (create in
>the Java Preferences section), then include the variable in the project.
>This way the only time people have to do anything about checking out a
>project is if there is a new variable created and included by the
>project, and even then, it only has to be created once.
>
>
Another possibility:

I'm using Apache Maven as my build tool (but I'm currently not using the
plugin because it's only available for Eclipse 3.0). Maven uses a
project.xml file which specifies all JAR dependencies. After checkout I
call a special Maven-Command which generates the .classpath and .project
files.

Jürgen

-- 
Juergen Baier