cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3397) Problem markers don't show up in Eclipse
Date Thu, 22 Dec 2011 22:13:30 GMT


Eric Evans commented on CASSANDRA-3397:

I wasn't aware of this issue when I submitted (and later committed) CASSANDRA-3632.  Have
you had the chance to try this again since?

CASSANDRA-3632 restored the default Java builder (so problem marks do show now), but I left
the Ant Builder out entirely.  I personally found it too heavy to be running, for example,
on every file save (I mash CTRL+S compulsively).  Do you find the Ant Builder useful or were
you primarily interested in restoring the error markers?
> Problem markers don't show up in Eclipse
> ----------------------------------------
>                 Key: CASSANDRA-3397
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 1.0.0
>         Environment: Eclipse
>            Reporter: David Allsopp
>            Assignee: David Allsopp
>            Priority: Minor
>              Labels: ant, eclipse, ide
>             Fix For: 1.0.7
>         Attachments: Cassandra-3397.patch
> The generated Eclipse files install an Ant Builder to build Cassandra within Eclipse.
This appears to mean that the default Java Builder is not present. This means that no problem
markers show up in the Problem view or the Package Explorer etc when there are compiler errors
or warnings  - you have to study the console output, then navigate manually to the sources
of the problems, which is very tedious.
> It seems to be possible to re-install the default Java Builder in parallel with the Ant
Builder, getting the best of both worlds. I have documented this on the wiki at
> I was wondering a) whether this can be done automatically by the generate-eclipse-files
Ant target, and b) whether using both Builders will be problem if one is working on any of
the generated code (Thrift, CQL etc). The Java Builder can be temporarily disabled if so by
unticking it under Properties->Builders...
> See also

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message