Ate Douma <[EMAIL PROTECTED]> wrote on 01/25/2008 09:35:43 AM:
> [EMAIL PROTECTED] wrote:
> >
> > +1 to svn:ignore
>
> Thanks Graig and the others for agreeing on this and I will proceed
> doing this shortly.
>
> >
> > I'd also like to see .classpath in the Pluto root and would not object
to
> > analagous files for IDEA and Netbeans IDEs. I cannot get the maven 2
> > eclipse plugin to create a single .classpath in my Eclipse project's
root
> > dir. I have to run 'mvn eclipse:eclipse' in the root dir, and then in
all
> > the module subdirs and then manually combine the resulting .classpath
> > entries into the root one. That is a pain.
> > /Craig
> Well, that is not how you are supposed to do it or use Eclipse in my
view.
> Although Eclipse still doesn't support nested projects (see long
> standing issue:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=35973
> and please cast your vote), but there is a simple "trick" to handle
> maven-2 kind nested projects in Eclipse (3.2+ AFAIK).
I just voted for this. Thanks for the info.
>
> Note: for this to work I had to switch from the subclipse plugin to
> the subversive plugin:
> http://www.polarion.org/index.php?page=overview&project=subversive
>
> But as subversive actually is a very good svn plugin and its core
> component now even an official Eclipse project, I never had a need
> to look back.
>
I've had good luck with subeclipse, but I'll give subversive a try.
> What I normally do is the following:
> - Check out the root of the project using Eclipse and call it
> <project-name>-trunk, so pluto-trunk)
> This will create a default, non-java .project Eclipse project
> file and thus also without .classpath.
> - Then run mvn eclipse:eclipse to generate the Eclipse .project and
> .classpath files
> - now comes the trick:
> - while having Eclipse running, delete its auto generated .
> project file from the file system
> and don't touch or refresh your trunk project while doing the
> following step
> - open the File..., Import..., Existing Projects into Workspace dialog
> - select as root directory for import your checked out project
> root folder and import the now displayed nested projects
> - press finish
> - Eclipse will automatically recreate the deleted ,project file
> for your project trunk project
>
> Now you have both the full project tree (under project
> <projectname>-trunk) as well as the all the nested java projects and
> you are ready to go.
So this is a way to fool eclipse into creating nested subprojects? How did
you figure this one out?!?
I'll see how it works, but I wish there was another way. Maybe you should
put this info on the Wiki?
>
> As this works quite neatly now with Eclipse (3.2+) I honestly don't
> think we should check in hand created (or one time generated) .classpath
files
> as these are a pain to keep properly in sync, especially when using
> nested projects.
>
I'll see how your subversive incantation and subproject yoga works (BTW,
what are those magic words again?).
At any rate, I think that Eclipse developers would update the .classpath
file as a matter of course when dependancies change,
but if there is no sentiment for this idea, I'm willing to drop it.
BTW, I have m2eclipse, but it is slow as molasses (in January). I have the
latest 'stable' version installed (0.0.10).
