intertwingly

I have to have a go back here. You've got it all wrong....

We want Jelly to get out of the sandbox. We've even all agreed it's a Good Thing.

I wouldn't call HttpClient 'unstable'. Maybe a bit quick to delete code, but not unstable.

And as for noone caring, boy are you way off again? Is it just your day for it :)

HttpClient is in a roll on their way to a new release, and as such the APIs are in flux. We are patiently waiting for some patches to go through so that we don't try to play catch up during this time.

Of course, if you'd like to donate the time and effort into reimplementing stuff today and then again in a few days, please contact me via email.....

Hi dIon! Loved your rant on the same subject.

Another subproject in perpetual alpha (even though they pretend it is beta) is Maven. Mind if I turn on the nag e-mails for this component?

Nudge, nudge.

P.S. The nice things about weblogs are that they are editable. I can't wait to issue a global s/SUCKS/ROCKS/g.

Consider us nudged ;). It will be fixed soon. Thankfully Gump will keep on nagging us until it gets fixed.

Incidentally, there's been a vote to move Jelly from the sandbox to the commons

http://marc.theaimsgroup.com/?t=103918410500001&r=1&w=2

so that should happen real soon as well.

During the move I hope to make Jelly's build process a little more modular so that the core of Jelly has far fewer dependencies and so has a more stable build system.

Btw you aren't keen either to move gump to use the latest stuff I guess :) (didn't get a reaction for my patches sent to alexandria) :)

James - all coolness!

Martin - touché. I'll get on it.

Sure, turn on nags for Maven.

Speaking of which, when will gump support Maven built projects as well as Ant built ones :)

Getting it bootstrapped is the hard part....

dIon - yes, bootstrap is the first issue. It would be nice if Maven does what James suggested above - have a minimal core with few dependencies, and a whole bunch of plugins.

Note that maven now needs forehead. But the maven generated gump descriptions are bad, so forehead won't build. My recollection is that this problem with Maven was fixed a while ago, but forehead hasn't kept up. Then I hear that forehead is deprecated. ARG! The fact that there exists a configuration in which maven works at all seems like a minor miracle to me.

The second, and final issue is that I need an option whereby Maven will use the versions of dependencies there were locally built instead of ones that it might download off of the internet.

P.S. nagging is now turned on for maven.

I regen'd the build.xml for forehead. Maybe gump'll be happy now.

Thanks, bob! I had to tell gump to include junit and where the jar is, but the next build (in about 19 hours) should succeed.

I added a whole bunch of dependencies for maven (forehead, werks, commons-logging, which). Now the only failures are Jelly (of course) and org.apache.commons.cli.CommandLineParserFactory which does not appear to exist.