On Sat, Apr 9, 2011 at 7:54 PM, Jörg Schaible <[email protected]> wrote: > Ludwig Magnusson wrote: > >> Hello! >> >> I know that the maven-eclipse-plugin somehow can figure out that a >> dependency actually exists as a project in workspace and therefore add >> that project to the build path instead of trying to download a jar-file >> from a remote repository. >> >> My question is: >> >> Is this possible for any dependency or just multi-module-projects? >> >> >> >> In my case, the project is NOT multi-module. > > Only multi-module. However, it is easy to use a dummy project (name it > dummy.pom) just for this purpose:
This should work for *any* dependency, that is already in your eclipse workspace. I do this already. We have one "common" area for projects and another project specific one. The project specific modules are not multi-module builds of the common ones. maven-eclipse-plugin will happily use any of the common projects as eclipse project references (instead of m2 repo references) if they already exist in the eclipse workspace. The plugin does this by traversing all projects in the workspaces and checking the pom.xml files to see if they match the GAV for the dependency. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
