On Thu, Jun 14, 2012 at 11:19 AM, Simon Helsen <[email protected]> wrote: > Paul's description is more or less how I handle it. > > The problem about components being independent, yet, the desire to have > their presence in Eclipse override this is not new of course. When I was > still working at SAP, we had a proprietary build system that could do this > and behaved exactly as you'd expect, i.e. if the component is loaded in > eclipse, it takes precedence over the downloaded built artifacts. The > build system we use at IBM (jazz.net) manages this by using eclipse target > platforms, but that only works because everything we do here sits in a > plugin. > > AFAIK, there is no proper solution to Jena's setup in Maven other than > manually fixing the classpaths > > Simon >
m2e handles this situation nicely. If a dependency version in your project's pom is the same as a matching open project, then it uses that automatically. If you change the dependency in your pom to a different version, change the dependency project's version, or close the dependency project, then it automatically switches to use your local maven repository. -Stephen
