the dev version of the m2eclipse plugin will automatically resolve project references when the depedency resolves to a snapshot...
you can run mvn eclipse:m2eclipse to generate the project files for the m2eclipse plugin update site... http://m2eclipse.codehaus.org/update-dev/ On Wed, 16 Jan 2008 08:14:29 TM wrote: > Hello, > > my question is about whether it is possible to let the Maven Eclipse plugin > create the ".classpath" file in a way that it will directly reference > dependency projects instead of referencing the JAR artifact from the local > repository. The following example .classpath file for a project named "foo" > illustrates this: > > <?xml version="1.0" encoding="UTF-8"?> > <classpath> > <classpathentry kind="src" path="src/main/java"/> > <classpathentry kind="src" output="target/test-classes" > path="src/test/java"/> > <classpathentry kind="con" > path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry > combineaccessrules="false" kind="src" path="/common"/> <classpathentry > combineaccessrules="false" kind="src" path="/system"/> <classpathentry > combineaccessrules="false" kind="src" path="/api"/> <classpathentry > kind="output" path="target/classes"/> > </classpath> > > The version above has three "direct" references to projects "common", > "system", and "api" which are all sibling projects, i.e., are located in > the same folder than project foo. Regarding Maven all four projects are > modules of a parent project. > > When I now start "mvn eclipse:eclipse" in project foo it will create a > .classpath file that looks like this: > > <?xml version="1.0" encoding="UTF-8"?> > <classpath> > <classpathentry kind="src" path="src/main/java"/> > <classpathentry kind="src" path="src/test/java" > output="target/test-classes"/> > <classpathentry kind="output" path="target/classes"/> > <classpathentry kind="con" > path="org.eclipse.jdt.launching.JRE_CONTAINER"/> > <classpathentry kind="var" > path="M2_REPO/org/blahh/common/1.0/common-1.0.jar"/> > <classpathentry kind="var" > path="M2_REPO/org/blahh/system/2.0/system-2.0.jar"/> > <classpathentry kind="var" path="M2_REPO/org/blahh/api/1.2/api-1.2.jar"/> > </classpath> > > The three projects are now referenced by the JAR artifact from the > repository. This is not optimal for me since changes to the code in one of > the three projects are not instantly visible to project foo (provided that > Eclipse' auto build is turned on); only after a Maven install rebuild. Is > there any option that I can use to force the Eclipse plugin to reference > dependency projects directly? If it doesn't exist yet, then take this as a > feature request. > > Thanks, > Thorsten -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
