Hi Tom,
(CCed classpath list since people there might find this interesting)
[For those not reading planet.classpath.org regularly, also check out:
 http://www.peakpeak.com/~tromey/blog/2005/08/18/#eclipse-classpath ]

On Thu, 2005-08-18 at 10:00 -0600, Tom Tromey wrote:
> I've set things up so that you can build Mauve as an Eclipse project.
> It requires you to also have a classpath project at the moment, and it
> uses the classpath classes for the bootclasspath of the mauve build.
> 
> To see this, use Eclipse 3.1, check out Classpath (and wait for it to
> build), then check out Mauve.  That should be enough, no configury or
> anything else should be required.

Very nice. I tried this with the new eclipse packages from Michael
(http://gnu.wildebeest.org/diary-man-di/index.php?p=21 - for which I
only needed to cheat with one --force-depends since tomcat4 isn't
available in main yet). And it seems to work for both classpath and
mauve.

The only trouble I had in both is that eclipse seems to not be able to
find any of the generated files, like gnu/classpath/Configuration.java
and gnu/testlet/config.java till I explicitly refresh the projects
manually. Which is a slight pain since it won't let me do that until
after it tries to compile everything and tries to show the hunderds of
errors it finds due to these missing files.

Cheers,

Mark

-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/