[commited] Check in of Eclipse Project files

Home Forum Archive Contribution Depot (jME2) [commited] Check in of Eclipse Project files

This topic contains 5 replies, has 5 voices, and was last updated by  Vardamir 6 years ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #11465

    Core-Dump
    9p
    Member

    I would like to check in the .classpath and .project files for eclipse projects.
    This makes it easier for new users to get started with jme2 and eclipse.

    Right now if you check out the jme project from svn you have two options:

    – "check out as project from svn'" or
    – "Check out as project configured using the new project wizard"

    If you choose the first option "as project from svn" then no java builder is set and the project cannot be compiled.
    What i do then, is delete the jme project (only from workspace, not the files), and create a new java project with the same name as the previously checked out. Now it has the correct Builder and classpath set.

    Even with checked in .classpath / .project, the user still has to set the native directory for the lwjgl.jar after the checkout, depending on the OS.

    .classpath:


    <?xml version="1.0" encoding="UTF-8"?>
    <classpath>
       <classpathentry kind="src" path="junit"/>
       <classpathentry kind="src" path="src"/>
       <classpathentry kind="lib" path="lib/jogl/gluegen-rt.jar"/>
       <classpathentry kind="lib" path="lib/jogl/jogl.jar"/>
       <classpathentry kind="lib" path="lib/jorbis/jorbis-0.0.17.jar"/>
       <classpathentry kind="lib" path="lib/junit/junit-4.1.jar"/>
       <classpathentry kind="lib" path="lib/lwjgl/jinput.jar"/>
       <classpathentry kind="lib" path="lib/lwjgl/lwjgl_util_applet.jar"/>
       <classpathentry kind="lib" path="lib/lwjgl/lwjgl_util.jar"/>
       <classpathentry kind="lib" path="lib/lwjgl/lwjgl.jar"/>
       <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
       <classpathentry kind="output" path="bin"/>
    </classpath>

    .project:


    <?xml version="1.0" encoding="UTF-8"?>
    <projectDescription>
       <name>jme 2</name>
       <comment></comment>
       <projects>
       </projects>
       <buildSpec>
          <buildCommand>
             <name>org.eclipse.jdt.core.javabuilder</name>
             <arguments>
             </arguments>
          </buildCommand>
       </buildSpec>
       <natures>
          <nature>org.eclipse.jdt.core.javanature</nature>
       </natures>
    </projectDescription>

    #86203

    dhdd
    2p
    Participant

    i guess there could be problems with older and/or newer Eclipse versions (?)

    #86204

    Core-Dump
    9p
    Member

    i think they are pretty generic and should be readable by any eclipse version, what i'm not sure is, if they conflict with other IDE's like netbeans or the like.

    btw, the jme physics 2 project has them checked in already also .

    http://code.google.com/p/jmephysics/source/browse/trunk/.project

    #86205

    keeskist
    0p
    Member

    The same .project and .classpath files are used by all Eclipse 3.x versions.

    #86206

    irrisor
    2p
    Participant

    We have .project and .classpath in most of our repositories at work. This should not be a problem for jME as well, if all people with write access are cautious with checkins of those file. Locally renamed eclipse projects must not be committed with .project etc.

    #86207

    Vardamir
    0p
    Member

    We also have .project and .classpath files in the repository. As long as there are no references to local resources (path names), there is no problem

Viewing 6 posts - 1 through 6 (of 6 total)

The forum ‘Contribution Depot (jME2)’ is closed to new topics and replies.