Could we just prevent that by overriding the maven:eclipse goal in the
projects' maven.xml and echo out a message stating a message that no
.classpath generation is necessary since these are already eclipse
projects?
FYI. The mevenide plugin is also including the .classpath in their repo.
Sachin.
Jeff Genender wrote:
Hmmm now that I think about this...
Sachin, these files will likely get overwritten when someone does a
"maven eclipse". Be prepared for these to get overwritten fairly
often, and will likely get rechecked in.
Jeff
Jeff Genender wrote:
Sachin Patel wrote:
Yes, I think this is needed. Since these are eclipse plugins to
begin with I consider these to be part of the project
configuration. Eclipse users should be able to directly import
these projects into Eclipse without having to generate the .classpath.
As long as these have no machine specific info in it then it may be
ok. ..ie same configuration that will work on Windows, Linux, and
Mac. But normally, I am against this. We usually use maven to
generate these files for us.
Jeff
Jeff Genender wrote:
I noticed these files going into the eclipse plugin:
UU sandbox/eclipse-plugin/org.apache.geronimo.ui/.classpath
UU
sandbox/eclipse-plugin/org.apache.geronimo.deployment.model/.classpath
UU sandbox/eclipse-plugin/org.apache.geronimo.core/.classpath
Are these ok? IIRC, these are user/computer specific to the user's
setup. Are these supposed to be checked in (.classpath)??
Jeff
