Hi Jan,
.project, .classpath and several other eclipse-specific files are
created by the maven eclipse plugin ( mvn eclipse:eclipse ).
Those created files contain appropriate contents regarding the maven
repository. E.g. .classpath gets entries pointing into your local maven
repository using a classpath variable M2_REPO.
The existing eclipse files in your scm probably contain still references
to libraries not in the repository. AFAIK that's the reason why you
should (re-)create them with the plugin ( commiting them to the scm
should be no problem as long as you are aware that you have to
recreate/update them when you change your pom.xml (e.g. new dependencies).
Regarding the lost connection to the scm - i think those information are
stored in the eclipse .metadata directory. Therefore it's not really
related to maven that the connection is lost as maven does not touch
that. I'm not sure about this - however I think that the term
"importing" is somehow vague. I can remember there's a "plain" import
which copies external files only into the workspace without any
metadata. Did you use that or something else ? Anyway an
"import"-mechanism should for your needs handle those .metadata stuff as
well. Otherwise the connection will be definitivly lost.
Regarding flat vs hierarchical layouts. None of both ways is the perfect
one. I tried both and for me it was more important to being able to work
with eclipse properly - therefore flat layout. A lot of the maven
plugins work with that. However there are several issues ( I had and
still have problems with the site plugin, the release plugin seems to
have it's problems as well). The bad thing about this actully is that
it's not always really clear what's working with the flat layout and
what's not. You have to try that for your project...
Regards
Alex
Jan Vissers wrote:
Hi,
(Using Maven 2.0.4)
I'm trying to figure out how to use a (Maven) multi module project in
Eclipse where Subversion is the SCM. Following the "Guide to using Eclipse
with Maven 2.x" somehow doesn't do it for me.
Things I don't understand:
+ why should I remove .project, .classpath ?
+ given the fact that I have indeed thrown about .project, .classpath
from the modules and have checked this in into subversion, how comes
that when I start a completely new workspace and import the modules
I end up with resources not being 'connected' anymore to subversion?
+ I've read somewhere that flattening the project layout, doesn't work due
to issues with the Maven release plugin. From JIRA it seems this is still
the case. Anyone now whether there are any workarounds for this and if
their are other issues in flattening the layout?
Thanks.
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
