« Ultimate | Main | links for 2007-04-17 »

Java Archive Network

Elliotte Rusty-Harold: "What's the real core of Java? The pieces you can't do without? java.lang, a few pieces of java.io and java.util "

I'm not Sun, but this is the kind of question I'd lob to Ian Murdock, now that he works there. As much as Debian's sluggish process annoys me, its packaging system represents the state of the art.

"Some sort of centralized system or user repository would hold different versions of various libraries. Maven already comes very close to this, and JSR-277 may go further."

Java could do with something like CPAN or Gems. As for JSR-277, I suspect if you hooked OSGi packaging into an Atom Protocol based distribution and publishing mechanism, threw in signing, avoided transitive dependencies, you'd have a technical basis for an archive network. But wow, not Maven.

April 15, 2007 07:58 PM


(April 16, 2007 06:39 AM #)

Yeah, *everything* but *not* Maven, please! :-)

It took me half a day to compile apache ode thanks to Maven not supporting a custom repository location (even if it let's you configure it).

Bill de hOra
(April 16, 2007 03:03 PM #)

"but *not* Maven, please! :-)"

You must be new here.

More seriously; archive management and packaging is a different job to building stuff. It's not as if the Perl, Ruby and Python communities decided to confuse make with autoconf with CPAN Gems and Eggs.

Ant and Ivy get this right by being separate components. Add archive management to complement those two, and you have have a full stack, without the monolith codebase. The maven doodads that are actually useful will get ported to ant tasks anyway.

Post a comment

(you may use HTML tags for style)

Remember Me?

Trackback Pings

TrackBack URL for this entry: