Pat,
I am having troubles to interpret your description. I would really
recommend to use step by step approach, explicitly describing actions or
menus you invoked, results you see and results you expected to see.
Also, there is a few things you mentioned are confusing and probably
good to know.
* "Nested Modules", I don't recall such option. There is a "Separate
projects for modules" option on the Maven project import wizards, and
"Include Modules" in the project properties
* "Existing Maven Project", I don't recall such option. There is a
standard Eclipse wizard called "Existing Projects into Workspace" and
one contributed by m2eclipse is called "Maven Projects"
* The "Team > Share..." action is used to do the initial commit of the
code to version control, i.e. "share a local project with the team"
* If you have corresponding version control system provider installed
(cvs, svn, etc), that provider is responsible for attaching imported
projects to the version control. you can verify if it is working by
checking out from the command line and importing your project using
standard Eclipse import wizard "Existing Projects into Workspace"
* the "Project Explorer" view is essentially a file browser. so, if your
projects are arranged hierarchically in a file system you will see
folders corresponding to the nested modules under the parent project.
m2eclipse contributes a spacial filter to the "Project Explorer" view in
order to hide these module folders to reduce confusion
* it is not recommended to disable "Separate projects for modules",
because it may lead to issues with dependency management and 3rd party
tool integrations, especially if you have projects with war, ear and ejb
packaging types
* Subclipse is known to not deal very well with nested projects,
especially if you are using Synchronze view, and to work around that I
suggest to only synchronize on the top most parent project and then
refresh the child ones if necessary (because they files will be there on
the file system)
* The m2eclipse provides an option for checking out from svn and other
version control systems. See the following wiki pages:
http://docs.codehaus.org/display/M2ECLIPSE/Importing+Maven+projects#ImportingMavenprojects-CheckoutMavenprojectsfromSCM
http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Subclipse
http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Subversive
http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Eclipse+Team+CVS
BTW, is anyone interested to contribute similar integration for egit
[1] or MercurialEclipse [2] ? More specifically, some kind of UI to
browse repository and revisions [3].
regards,
Eugene
[1] http://git.or.cz/gitwiki/EclipsePlugin
[2] http://www.vectrace.com/mercurialeclipse/
[3]
http://docs.codehaus.org/display/M2ECLIPSE/Extension+Points+and+API#ExtensionPointsandAPI-scm
CheffPJ wrote:
I had trouble doing an initial SVN import on several multi-module projects.
Using:
* Eclipse 3.4.1
* m2Eclipse 0.9.7.2009.02090947
* Subclipse 1.4.7 (??)
* Nested Modules: Disabled
I had several multi-module projects that I was looking to import to SVN
(i.e. check-in for the first time). I figured it would be easiest to just
do a recursive import from the module-owner projects. But after selecting
(Team > Share...), I found the module projects hidden. I wasn't all that
surprised to see that considering the modules were represented as
independent projects in Project Explorer. But at the same time, project
explorer definitely shows the nested directories within the module-owner
project itself, so I wasn't sure what to expect before I did it. I checked
in the module-owner projects anyways, even with the modules hidden from me.
At that point, I could have probably gone to each individual one of the
module projects and done a (Team > Share...) and made sure to manually
select the correct existing directory (from the ones I just checked in), but
then I would risk human error in putting them in the wrong place. Frankly
though, the real problem here is that I'm just lazy and that would have been
a PIA b/c I'm talking about like 10 modules (JBI, what can I say).
So, I removed all my projects from eclipse, re-imported them (Import >
Existing Maven Project) and made sure to un-check "Separate Projects for
Modules." With that done, eclipse now treated my modules like
sub-directories, and I was able to check-in as I originally expected. Then
remove all the projects again, re-import with separate projects for modules,
and I'm back to normal.
I think some better functionality would be nice, maybe something that allows
you to use something equivalent to command-line style recursive check-in,
even when teh directories are "hidden" due to module structure. Maybe this
is more of a problem in the SVN client, in that it doesn't notice the parent
directory has SVN metadata.
$0.02,
Pat McDonough
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
