All, Thanks for all the helpful feedback. I don't have any more time to look at this today, but I'm sure there's enough here to get me up and running.
My two cents, FWIW: there's a wide enough variety of development environments, preferred workflows, etc. on distributed teams that it's difficult to come up with a common set of .classpath/.project/.settings files that works for everybody, and it's better to just omit that stuff from the repository and let Maven generate it. Of course, if there are other technical reasons it can't be done right away (such as command-line tools that use .classpath) then that can't be helped. At the very least, I think it would be helpful to have a list of instructions on the website next to the SVN link on how to get set up in Eclipse from a fresh checkout. I think good goals for a recommended Eclipse set-up would be: 1. Inter-project dependencies are resolved by references to Eclipse projects, not the local Maven repo. 2. "svn status" in the root directory reports no changes. If I make progress on this front I'll be happy to share what I have with you. Thanks, Alex On Thu, Jun 14, 2012 at 3:55 PM, Stephen Allen <[email protected]> wrote: > 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 >
