If I understand correctly then I agree with McClain, its out of whack.
One of the main reasons of having a version control system is to have
individualy checked
out repositories where developers can work and stay out of each others way.
If you were to use a single network 'share' as the source of files
worked on, your eclipse will have to be continiously refreshed as its
idea of the file system will constantly change outside its control.
Also as soon as you save (not commit) everyone else will get your
possibly whacky unstable idea of the next version without you being
able to test it locally and sanitize it first as would be the case
with a normal local repository. I don't know about you but I press
save pretty often, must be a side-effect of using vim.
There must be better ways to solve complex dependencies. If its just
on jars that already exist, then you can set up a project in eclipse
that only contains all the dependency jars. If you really want you
can put this on a network share, but not commit to version control.
If the dependencies are on source code then you have at least 2 choices:
1) Stop relying on eclipse to do everything for you and use something
like Maven outside of Eclipse which will resolve your dependencies.
2) Use the eclipse feature of projects depending on projects and find
a way to share the eclipse configuration files that contain this
information.
--
Alwyn Schoeman
Mid-life crisis in action
Received on Sat Jul 10 01:42:40 2004