I would like some advice on setting up a multi-project workspace using Eclipse. In other words, I intend to create some kind of application that will use two or more projects for its final assembly. Projects will be stored in some version control system. This is pretty easy to do.
The tip I'm looking for is how I should set up version control or the Eclipse workspace to make it easier to set up a new developer / new machine. Ideally, a new developer or a developer on a new machine just issues one command (to something: it could be Eclipse, a version control system, some build system, or even a script); this command will create an environment from which code can be created.
I will use Java for the language and Mercurial for version control, if that matters for the solution. I am open to using the build system, although I have almost no acquaintance with any of them.
In fact, I hope to learn
- where projects should be stored in the repository
- how Eclipse should import or otherwise discover projects
- how to initiate the above detection
* In this case, the new computer means a machine with the necessary applications (for example, Eclipse and TortoiseHg), but without code checks or any workspaces
java version-control eclipse
Eric
source share