building with eclipse

building with eclipse

[Tom Tromey]

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.


An idea for the future would be to add a standard launch
configuration so that you can easily run mauve using the just-built
classpath on jamvm.

A more complicated idea would be a test-running GUI of some sort
(standalone or an Eclipse plugin) that would let you pick subsets of
the tests, see regressions, see what tests are new, etc.

Tom

Re: building with eclipse

[Mark Wielaard]

[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]

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/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: building with eclipse

[Tom Tromey]

>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:

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

Hmm... this should happen already.

Pull up the project properties for the classpath project.  Then go to
the Builders tab, pull up the Autogen builder, and look at its Refresh
tab.  For me it says to refresh "the project containing the selected
resource".

I guess we could experiment with changing that to "specific resources"
and specifying the appropriate directories.

Tom

Re: building with eclipse

[Mark Wielaard]

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

Hi Tom,

On Mon, 2005-08-22 at 13:30 -0600, Tom Tromey wrote:
> >>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
> 
> Mark> The only trouble I had in both is that eclipse seems to not be able to
> Mark> find any of the generated files, like gnu/classpath/Configuration.java
> Mark> and gnu/testlet/config.java till I explicitly refresh the projects
> Mark> manually. Which is a slight pain since it won't let me do that until
> Mark> after it tries to compile everything and tries to show the hunderds of
> Mark> errors it finds due to these missing files.
> 
> Hmm... this should happen already.
> 
> Pull up the project properties for the classpath project.  Then go to
> the Builders tab, pull up the Autogen builder, and look at its Refresh
> tab.  For me it says to refresh "the project containing the selected
> resource".

Just did a clean classpath CVS checkout with a cleanly installed eclipse
(new debian packages from Michael) with no old .eclipse or workspace
directories. Which gave the same result as described above.

Properties -> Builders -> Autogen -> Refresh has "Refresh resources upon
completion" checked, "The project containing the selected resource"
checked and "Recursively include sub-folders" checked. Similar for the
Configure builder.

Selecting refresh on the classpath project fixed the problem as before.

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/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: building with eclipse

[Tom Tromey]

>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:

Mark> Just did a clean classpath CVS checkout with a cleanly installed eclipse
Mark> (new debian packages from Michael) with no old .eclipse or workspace
Mark> directories. Which gave the same result as described above.

Unfortunately I don't know what is wrong :-(
I haven't tried a fresh checkout in a while due to the cvs problem in
the FC eclipse.

BTW, this weekend I set things up here so that I can have jamvm and
classpath in the same eclipse workspace, set up so that jamvm uses
the just-built classpath with no extra steps.  I haven't set up any
canned launch configurations yet, but that is also easy.

Tom