Comments on: Eclipse Callisto: Success or Failure?

By: Archimedes Trajano

Archimedes Trajano — Tue, 13 Mar 2007 07:44:14 +0000

It would be nice if Maven were just run as a set of plug-ins but on the Eclipse framework. Not that plexus is a bad thing.

The intent is to remove more code from Maven and offload the maintenance of it to other opensource projects.

A side effect of this would be Maven can work as a plug-in in Eclipse as part of its core feature rather than an afterthought (e.g. mevenide or maven-eclipse-plugin). Those two projects are great, but can get out of sync with the rest of Maven.

By: Damien

Damien — Sun, 06 Aug 2006 09:08:26 +0000

Maven can build easily and with success OSGi based softwares, even Eclipse based applications.
OSGi allows you to have many and many modules in you apps, Maven able you to handle them all together

By: Tim O'Brien

Tim O'Brien — Fri, 04 Aug 2006 14:37:29 +0000

…because, even in a “well modularized environment”, you still have to worry about interfaces between modules, common documentation practices, etc. I wouldn’t view this as a failure of modularity as much as an attempt to synchronize effort and resources across multiple groups. I see this more as an attempt to galvanize the people involved and focus the effort.

By: Brett Porter

Brett Porter — Tue, 04 Jul 2006 10:58:02 +0000

Hey James! It’s interesting that you put the “get it all in one place” argument as the best thing, and the “known, compatible versions” argument as an added bonus, as most of the Callisto hype I’ve read has been focused on the latter.

These are both good things, though I’m not sure that simultaneous releases are necessary to achieve the first goal.

As for the known compatible versions - that was really my point - certainly a good thing to have, but why is it necessary in a well modularised architecture?

By: James Strachan

James Strachan — Tue, 04 Jul 2006 02:24:16 +0000

So eclipse is very modular and you can install whatever versions of things you need.

The power of Callisto is that once you have hundreds of eclipse components (developed at eclipse.org), spread around many different repositories - it can take a while to choose what you need and install them all. So really its just about having a shared repository really
The big win of Callisto from an eclipse user (and ex IntelliJ user too is that at last all the dependencies of things like WTP are in one repo - whereas before the common base plugins like EMF and GEF were not even in a repo causing heaps of manual download.

The added bonus of Callisto is it provides a simple single version number that folks who use most of Callisto (eclipse + WTP + BIRT + Data Tools + TPTP say) don’t have to play version bingo, but can just upgrade to known, compatible versions