How to use Eclipse and version control for the project matrix
Our company develops several software products that reuse each other's packages (we use Java). Each product is presented as a separate Java Eclipse project and has its own version repository (we are using Mercurial).
When we find a bug in some common package, we need to push the changes to all consuming projects, and that's hell. The main problem is that an Eclipse project can only be linked to one version store.
Can someone recommend some way to link an Eclipse Java project with multiple version repositories that can ideally be heterologous (svn, git, mercurial)?
a source to share
This really needs to be addressed:
You can modify directly from the submodule / sub-repo, push to the "central" repo and the other is to commit the changes, then go up one directory (basically the repo, referencing all other sub-modules) to register a new commit of the new state of the sub-module / sub-repo ...
The "main project" (the main repo in which all other submodules / sublocations are written) does not need an Eclipse project (one of the submodules can be the main Eclipse project, with project dependencies on the other).
See "The True Nature of Submodules " for more information on this process, which remains "tricky" but can still be precisely controlled.
a source to share