Hi!
First of all thanks for a very great plug-in! It has really made our
lives easier and encouraged the use of both Maven and Eclipse.
Our project have quite a lot of different modules and submodules:
: [EMAIL PROTECTED] ~/Documents/workspace/t2;find . -name pom.xml | wc -l
179
We've traditionally used m2eclipse with the "Enable nested module"
tick box on, but we're running into various issues because of the
massive joint classpath, which makes it easy to forget to add
dependencies to the POM, etc, tests failing because the wrong version
of dependencies are picked up, etc.
Our project is (unfortunately) still using CVS hosted by SourceForge,
and we use the Team->CVS functionality of Eclipse to check out, commit
and pick up updates.
I wanted to try changing to using the "multiple project" approach as
from File->Import->Maven projects. I don't think there's a way to
convert a checked out project (with the Maven dependency management
enabled) to multiple projects, so I copied the directories from my
workspace to a new directory, and then did the File->Import->Maven
projects.
I run into a couple of issues when having the "old" mega-projects
open, as they got picked up as project dependencies, which gave me
cyclic dependency issues. I closed all the old mega-projects and did
Maven -> Update dependencies - which worked perfectly and picked up
the nested-module-projects instead.
However, after doing this I no longer can commit changes or pick up
updates from CVS, although the CVS/ directories have been copied over.
Although I know this is not the Eclipse CVS mailing list, is there a
trick to "reconnect" the CVS connection again after importing these
projects? Or would it work to import directly from the directory of
the already checked out mega-projects, and do the commits and updates
from those? If so, then I think it's a bit tricky because of this
dependency-issue I mentioned above, I have to do the the
open/close-dance for each CVS update.
I noticed on
http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Eclipse+Team+CVS
that it's possible (in the upcoming version?) to check out as Maven
directly from the CVS repository perspective. This would be brilliant!
When is the next version coming out?
I assume this would enable the CVS "nature" of the projects so that I
can later do Team->Update and ->Commit and so on..?
I have Eclipse 3.4.0 j2ee with m2eclipse 0.9.5.20080717-1821 tried
using "Check out from SCM" typing in a very difficult URL
(ext:[EMAIL PROTECTED]:/cvsroot/taverna:t2core) - but
to no success:
7/29/08 11:27:42 AM BST: cvs : failure
7/29/08 11:27:42 AM BST: cvs : /bin/sh -c cd
/Users/stain/Documents/workspace/t3 && cvs -z3 -f -d
:ext:[EMAIL PROTECTED]:/cvsroot/taverna -q checkout -r
HEAD -d maven.1217327259098 t2core
7/29/08 11:27:42 AM BST: Checkout error; The cvs command failed.
(funnily if I try this manually on the command line everything works:
: [EMAIL PROTECTED] ~/Documents/workspace;/bin/sh -c cd
/Users/stain/Documents/workspace/t3 && cvs -z3 -f -d
:ext:[EMAIL PROTECTED]:/cvsroot/taverna -q checkout -r
HEAD -d maven.1217327259098 t2core
U maven.1217327259098/.cvsignore
U maven.1217327259098/checkstyle.xml
U maven.1217327259098/pom.xml
(..)
is this an issue with RSYNC_RSH=ssh (which I've set) or ssh-agent..?)
If this had worked - would I then get the CVS "nature" enabled?
Another related question.. what happens if I go for the
multiple-project set-up and a colleague of me checks in a new nested
module - how do I pick it up? In our current "Enable nested modules"
set up it's just a matter of doing a CVS update and "Update project
configuration" (previously: "Update source folders").
--
Stian Soiland-Reyes, myGrid team
School of Computer Science
The University of Manchester
http://www.mygrid.org.uk/dev/blog/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
