[daisy] Daisy with Eclipse

[Aaron.Digulla at Globus.ch]

daisy-bounces at lists.cocoondev.org schrieb am 20.09.2006 09:26:32:

> > I want to use the great Synchronize view of Eclipse, that's why I 
checked 
> > out Daisy into the workspace.
> it's a common itch with the maven-eclipse combination
> I typically have the current setup in such cases:
> 
> - checkout the top level in your workspace, use that to sync via
> subclipse, keep it a 'simple project' in eclipse terminology

I did that.

> - additionally add 'java projects' for the different subprojects, by
> pointing to a custom project-directory

I do that as well. I cannot create these as new project but I can import 
them.

The problem is Subclipse because as soon as I start doing this, the CPU 
usage goes to 100% until I either stop Eclipse or close these subprojects. 
Unfortunately, I can't see if JDT or Subclipse causes this.

> > Unfortunately, with this setup, it's impossible to import the 
sub-projects 
> > individually. I guess I'll stick to using one huge project. Thanks 
anyway.
> 
> it should be possible, but IIRC the limkitation (in eclipse) is that
> 'java projects' can't be pointing to nested directory-stryuctures,
> that's why you need to remove the 'java nature' from all directories in
> the hierarchy that contain sub-projects

To make sure I got this right: You say if have to remove the java nature 
from "/daisy" so I can create a new java project with the sources in 
/daisy/install?

I didn't try this. Maybe this would help with the CPU bug.

...

Ok, now, I've tried. I remove the java nature from the .project file in 
"/daisy" itself and then imported daisy-runtime-dependencies. That worked.

Then I did the same with the projects under "/daisy/services". Eclipse 
took a short timeout (2 minutes) to refresh the workspace. Then, it 
started thinking about building the workspace ("Building workspace 0%...") 
for about five minutes. Then it did compile for a minute or so.

But since the import, the CPU usage is at 100% and won't drop.

Therefore, I disconnected the subprojects from SVN. That took some time 
but finally, the CPU calmed down. So I guess it's a but in Subclipse (when 
there are the same resources in more then one project).

But working with disconnected subprojects just doesn't cut: I'd have to 
use the big daisy project to synchronize and use the subprojects to edit. 
That's almost as bad as using two Eclipse instances. Also, it doesn't make 
building much more simple (since the Maven plugin doesn't work with 3.2 
:-( )

I guess that these subprojects just don't work with Eclipse 3.2 and 
Subclipse.

> in eclipse 3.1 the nesting limitation was even worse: at one point
> trick was even to create two separate workspaces and run 2 eclipse
> instances: one to sync and manage the top-project, another to actually
> code inside the subprojects (all pointing to the same checked out
> code-sandbox on disk)

That would have been the next thing I'd have tried.

Regards,

-- 
Aaron Digulla