Greg Irvine wrote:
> However, why would you not want to add .project and .classpath to your
> repository. Surely you want to keep a record of the external
> dependencies etc for your projects so that when you "Check Out As
> Project" you automatically have the project dependencies set up. If you
> upgrade your Eclipse you'll have to check out the code again so why make
> yourself have to set up those dependencies again?
For my projects, I keep .project and .classpath files in the
repository as you mention. But this _does_ give problems for
Subclipse: a "Checkout As..." will fail.
The reason: before actually checking out the project, Subclipse
locally creates a new Java project. This makes sure that the
destination directory exists, and already creates a .project file in
that directory.
Next, it checks out the code, but this fails: Subversion refuses to
overwrite the locally created .project file with the checked out
.project file, and the checkout won't continue.
Kind regards,
Arnout
Received on Mon Mar 8 19:51:27 2004