i2p.i2p/apps/jrobin/.classpath

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry exported="true" kind="lib" path="jrobin-1.5.9.1.jar"/>
	<classpathentry kind="output" path="build"/>
</classpath>
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>`
Eclipse classpath consolidation 2013-11-21 09:38:09 +00:00			`<classpathentry exported="true" kind="lib" path="jrobin-1.5.9.1.jar"/>`
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>`