Too much pain and agony...
You can always export various settings etc, use a common set of
templates etc. In a perfect world everyone could have the same setup,
but with different developers on different versions of OS, and the fact
that every variation of plugins and Eclipse versions has enough bugs to
restrict it to only doing certain things it just isn't worth it. This is
one reason for using Maven, you can at least enforce a consistent build
environment from the command line everywhere.
Eugene Kuleshov wrote:
Eclipse configs don't really need to have any absolute paths, unless
of course you choose to use absolute paths in the .classpath, but it
is not an Eclipse issue.
I found it a very good practice to have all Eclipse-related project
configuration in version control (including per-project configuration
in .settings, such as code formatting, setting for warnings,
templates, etc). that helps to unify code standards across the team
and remove any assumptions about settings you may have locally in your
IDE.
regards,
Eugene
Tod Harter wrote:
Because then you couldn't just copy your workspace to another
filesystem and keep using it... As it is the workspace is totally
self-contained. Granted the setup and versions of Eclipse using it
need to be reasonably compatible. We don't version control .classpath
or .project files, so their presence is not really a problem, if you
svn checkout the project there is not a trace of the fact that you
used Eclipse to develop it.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
