...
- Create a "Linked Resources" Directory
- Technically, you can skip this step, but, it does insulate you from path differences between developer machines, since these would need to be absolute paths otherwise.
- Set up a linked resource path called "PROJECTS_DIRECTORY" with the appropriate path for your system.
- Add linked directories for each source path.
See the snippet below and adjust for your project name and path.
Code Block title .project linkedResources section type xml <linkedResources> <link> <name>sampleu-src</name> <type>2</type> <locationURI>PROJECTS_DIRECTORY/projectname/src</locationURI> </link> <link> <name>sampleu-test-src</name> <type>2</type> <locationURI>PROJECTS_DIRECTORY/projectname/test/src</locationURI> </link> </linkedResources>
- Add Linked Source Directories to classpath
Yes, you can do this with the UI, but editing the .classpath directly is easier.
Code Block title .classpath linked source directories type xml <classpathentry excluding="**/.svn/**" kind="src" path="sampleu-src"/> <classpathentry excluding="**/.svn/**" kind="src" path="sampleu-test-src"/>
- Add the libraries to the classpath
- Edit your build path to reference the libraries from your other project as needed.
...