On Sat, Mar 29, 2008 at 9:52 PM, Mark Webb <[EMAIL PROTECTED]> wrote: > "mvn install" will copy the jar file into your local repository. That is > why people say to run that first. I am sure that my instructions may be > somewhat inadequate, but I can confirm that they work.
Yeah, I'm familiar with mvn install :-) It's just that it should not be needed in this case since Maven will create a .classpath file that refers to the project, not the artifact. Note that the instructions you posted will differ in this regard as the .classpath files with refer to the artifact instead. Of course, the way you want it is a matter of taste. Hers's the diff for the core module for example: $ diff .classpath-all .classpath-standalone 10,11c10,11 < <classpathentry kind="src" path="/commons-net"/> < <classpathentry kind="src" path="/ftplet-api"/> --- > <classpathentry kind="var" > path="M2_REPO/commons-net/commons-net/2.0.0-SNAPSHOT/commons-net-2.0.0-SNAPSHOT.jar"/> > <classpathentry kind="var" > path="M2_REPO/org/apache/ftpserver/ftplet-api/1.0.0-SNAPSHOT/ftplet-api-1.0.0-SNAPSHOT.jar" > > sourcepath="M2_REPO/org/apache/ftpserver/ftplet-api/1.0.0-SNAPSHOT/ftplet-api-1.0.0-SNAPSHOT-sources.jar"/> classpath-all is the file created when mvn eclipse:eclipse is run from the root of the project. .classpath-standalone is created when the same command runs in the core module. /niklas
