Coming from IDEA I wouldn't settle for anything less than the 2.1 of eclipse, even it was still shaky at the time. Real men should not be afraid of any latest and greatest, only the last 2.1-RC1 broke my activity on the hibernate testing quite a bit...While everything worked in plain ant and in eclipse 2.1-M4, it would give me a quite odd 'ClassCastException' on the interpretation of a <taskdef> in the newest release.

After some needless looking into maybe incompatible jars and classpaths I went into stupid trial and error mode with some succes. I added my workarounds finally in their bugzilla and am now starting to wonder if a task like <taskdef> shouldn't always be inside a target. Stating that it just works in plain ant is maybe not the real argument? Have to check some ant code and doco's I guess. It shows in every case that the ant-build-file-parser inside the eclipse-ant-view is redoing (differently) stuff done already by the ant run-time...

The good news on the RC1: //TODO now adds directly the item into the Tasks View

One last thing, I promised Tom I would praise his eclipse consulting skills.

*update* snap eclipse developers have found the bug to be somewhere in their fast-parsing for targets that is in their ant-view thingy.... So trying to find a CCE reason I guess they just try to map all direct childnodes of <project> to be of type <target> or something?

11:04:50 PM    

We have the saying "goede wijn behoeft geen krans" -- something like "Quality doesn't need appraisal"

Yet, this feather will be worn with pride, I'm sure.

And shamelessly joining in the pride: This makes the percentage of apache-commiter-employees at outerthought jump from 66% to 100% again :-)

I guess this is a time where he would consider maintaining a blog :-)

3:56:43 PM    

more then words...

1:44:49 PM    

This is just fun: a new way to get to blue-underlined-words-I-can-click-upon! (gotcha ;-))

These got my immediate attention:

• findU operates some network of weather stations. This one is active in determing my mood.
• and some else is sharing interests (geo gadgets | calvin and hobbes | war opinions | XML | and a blog)

By the way, mozblog nuked one of my blogs again, have to take a look to this nucleus thing.

9:39:18 AM    

It only got better... read this and weep. Quoting only the yesyesyes-nodding-part:

A project requires:

• A Vision
• A need fulfilled (the itch)
• Users that will like "the way" how it works (for one reason or the other, be it simplicity of design, economy of resources, stability, cost, or even features ;-)
• + Management to keep it evolving and avoid it falling into pieces in the contrast between the needs of the users and the needs of the design
• Some "brand" that makes it easy for people to remember it exists
• Documentation
• A evolving developer team to fix bugs, document and re-structure code on a continuous base
• ... and a bit of code

The rest (I didn't quote) is downright helpfull and newbie supportive stuff: "way to go".I hereby declare 'Santiago Gala of hisitech fame' as my hero of the day.

9:27:20 AM    

I think therefore I do those activities somewhere... The statement can be verified officially, you just need to come over to

8:20:45 AM