echelon/i2p.i2p
1
0
Fork 0
forked from I2P_Developers/i2p.i2p
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
37d3204e433a887f2ba8e0776f056b7cde7e236c
i2p.i2p/apps/desktopgui/.classpath

10 lines
452 B
Plaintext
Raw Normal View History

Added .project and .classpath Eclipse files to most sections of the source To import a branch of trunk into Eclipse, create a new workspace based in the root directory of the checked-out branch, and then select "File -> Import..." then "General -> Existing Projects into Workspace", then for "Select root directory" choose the root directory of the branch (and of the workspace). Select all projects that appear, so that dependencies are satisfied. Currently left out are i2psnark, routerconsole and susimail, because they all depend on jars in apps/jetty/jettylib, which seems to be auto-generated. Need to check whether the existence of that folder (from having Eclipse files in it) will prevent the jars being populated or not.
2012-11-23 12:20:26 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="src" path="src"/>
<classpathentry combineaccessrules="false" kind="src" path="/i2p_router"/>
<classpathentry combineaccessrules="false" kind="src" path="/i2p_sdk"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
Eclipse project for entire installer dir
2014-05-21 02:02:36 +00:00
<classpathentry combineaccessrules="false" kind="src" path="/installer"/>
Added .project and .classpath Eclipse files to most sections of the source To import a branch of trunk into Eclipse, create a new workspace based in the root directory of the checked-out branch, and then select "File -> Import..." then "General -> Existing Projects into Workspace", then for "Select root directory" choose the root directory of the branch (and of the workspace). Select all projects that appear, so that dependencies are satisfied. Currently left out are i2psnark, routerconsole and susimail, because they all depend on jars in apps/jetty/jettylib, which seems to be auto-generated. Need to check whether the existence of that folder (from having Eclipse files in it) will prevent the jars being populated or not.
2012-11-23 12:20:26 +00:00
<classpathentry kind="output" path="build"/>
</classpath>
Reference in New Issue Copy Permalink