Ben, you might want to look at buildr, it recently graduated from the
"Buildr is a build system for Java applications. We wanted something
that’s simple and intuitive to use, so we only need to tell it what to
do, and it takes care of the rest. But also something we can easily
extend for those one-off tasks, with a language that’s a joy to use. And
of course, we wanted it to be fast, reliable and have outstanding
Also Ivy just released version 2.0.
If you have a specific idea and would like to start working on this
please create a JIRA to discuss/track/vote/etc... Be aware that the
contribution process, release process and other documentation would have
to be updated as part of this. For example if we want to push jars to an
artifact repo the artifacts/pom/etc... would have to be voted on as part
of the release process.
Benjamin Reed wrote:
i'm ready to reevaluate it. i did the contrib for fatjar and it was
extremely painful! (and that was an extremely simple contrib!) we really
want to ramp up the contribs and get a bunch of recipe implementations
in, so we need something that makes it really easy. i'm not a fan of
maven (they seem to have chosen a convention that is convenient for the
build tool rather the developer), but it is widely used and i we need
something better, so i'm certainly considering it.
Anthony Urso wrote:
Speaking of the contrib section, what is the status of ZOOKEEPER-103?
Is it ready to be reevaluated now that 3.0 is out?
On Fri, Jan 9, 2009 at 11:58 AM, Mahadev Konar <maha...@yahoo-inc.com>
It would be great to have such high level interfaces. It could be
something that you could contribute :) . We havent had the bandwidth to
provide such interfaces for zookeeper. It would be great to have all
recipes as a part of contrib package of zookeeper.
On 1/9/09 11:44 AM, "Kevin Burton" <bur...@spinn3r.com> wrote:
OK.... so it sounds from the group that there are still reasons to
rope in ZK to enable algorithms like leader election.
Couldn't ZK ship higher level interfaces for leader election, mutexes,
semapores, queues, barriers, etc instead of pushing this on developers?
Then the remaining APIs, configuration, event notification, and
can be used on a simpler, rope free API.
The rope is what's killing me now :)