You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@excalibur.apache.org by Leo Simons <ls...@jicarilla.org> on 2004/06/15 11:48:29 UTC

[RT] so...many...components...

Hi gang!

While on the subject of moving things back and forth between projects, 
lets briefly revisit this one as well. Sorry about the lenghty e-mail, 
but I think some people need some context. If you have the context, skip 
to the last paragraph.

What is Spice?
--------------
Spice is a component repository:

     http://spice.codehaus.org/

it's primary developer is Peter Donald, who is also the guy who wrote 
most of the excalibur component code. IIRC some of the materials in 
Spice are forks of excalibur materials and others are forks of 
cornerstone materials.

Again, IIRC, Pete started spice (over at sourceforge) when we decided @ 
avalon that we didn't want to host a component repository inside avalon. 
The bits of avalon that he moved over were the bits he was the primary 
(often only) maintainer for.

What happened?
--------------
All this got off to a bad start. I have no particular desire to drag all 
that up again. Instead of avalon materials being deprecated in favour of 
the spice ones, lots of nasty shit happened.

The current situation is that we have more than a little duplication of 
functionality between avalon, excalibur and spice, sometimes duplication 
of code (I think Pete improved a lot of the packages over at spice), 
etc, with the primary developer of some components having forked them 
offsite to develop them there, but all the old materials still lying 
around over here, mostly unmaintained.

Cocoon?
-------
ECM actually started within cocoon and moved over here. Along with it 
came bits and pieces of other code, in particular some of the 
components, like xmlutil and sourceresolve. Some of these saw use in 
other people's projects, others never did.

Cocoon uses ECM, but is AFAIK moving away to their own highly 
domain-specific solution. That'll take them at least a year or two (my 
estimate, not theirs!) before a final release. In the meantime we have a 
big ECM client to support.

Stefano and others have been crying out about the large amount of cocoon 
dependencies 
(http://cvs.apache.org/viewcvs/~checkout~/cocoon-2.1/gump.xml), and 
they've set out to reduce those.

This might mean cocoon will fork things like sourceresolve, which 
they're still going to need in some form.

So....many....repositories...
-----------------------------
Spice is just one of a multitude of IoC component repositories. Cocoon 
is just one example of an IoC-container-client.

In the meantime, avalon has also decided that they are going to keep a 
component repository around after all (I think its now called "Avalon 
Planet").

There's also the dormant but not dead idea of a ComponentHaus, which 
would contain dependency injection (you know, pico stuff) as well as 
service locator (you know, avalon) style IoC components. Mike Hogan 
started some basic code to automate that, then ran out of steam. I think 
Paul Hammant has his mind set on making this happen one day, which makes 
it likely that it will happen.

And there's more.

Turbine has IoC components. Cocoon has IoC components. Excalibur has IoC 
components. Avalon has IoC components. Spice has IoC components. Spring 
has IoC components. WebWork has IoC components. Keel has IoC components. 
Plexus has IoC components. Maven will have IoC components. PicoContainer 
has IoC components. ComponentHaus has IoC components. Lots of IoC 
materials scattered around the open source world.

Compare this to Jakarta-Commons, which is like the de-facto place to get 
some common "jdk additions". I don't see many people compete with 
commons-lang or commons-cli, at least not very successfully.

Now what?
---------
My take on all this is pretty simple: I have no particular desire to 
keep all this duplication of effort in place. It's an end-user nightmare 
and highly inefficient for the developers.

I would like to see the remaining components in excalibur moved 
elsewhere or deprecated in favour of packages living elsewhere, and 
focus on building a highly competitive container package. Projects like 
Keel can then compete with offerings like spring.

Oh, I usually make a distinction between "end user components" that you 
run inside a container and "building blocks" that you use to build a 
container. I'm talking about /both/ here.

Proposal?
---------
Nope. I would like to take a week or so to figure out what y'all are 
thinking, figure out what our average direction is, distill a plan, get 
it in jira, and JFDI.

WDYT?


cheers,


- Leo

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Re: [RT] so...many...components...

Posted by Leo Simons <ls...@jicarilla.org>.
Leo Simons wrote:
> Nope. I would like to take a week or so to figure out what y'all are 
> thinking, figure out what our average direction is, distill a plan, get 
> it in jira, and JFDI.

Summary: the basic sentiment "what a load of code! What a load of 
duplication" is one shared by just about everyone, coupled with concerns 
like "I'm using this, don't nuke it".

I like Pete's suggestion of taking this general but vague consensus on 
direction and applying it to individual bits and pieces of code in a 
gradual way.

cheers,

- LSD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Re: [RT] so...many...components...

Posted by peter royal <pr...@apache.org>.
On Jun 15, 2004, at 5:48 AM, Leo Simons wrote:
> There's also the dormant but not dead idea of a ComponentHaus, which 
> would contain dependency injection (you know, pico stuff) as well as 
> service locator (you know, avalon) style IoC components. Mike Hogan 
> started some basic code to automate that, then ran out of steam. I 
> think Paul Hammant has his mind set on making this happen one day, 
> which makes it likely that it will happen.

ComponentHaus needs to come to fruition. We just need a central 
catalog, that's all, really.
-pete


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Re: [RT] so...many...components...

Posted by peter royal <pr...@apache.org>.
On Jun 16, 2004, at 8:40 AM, Berin Loritsch wrote:
> XMLUtil is another beast entirely.  Apparently it is very important to
> Cocoon, and I believe Carsten Zeigler used it in some other non-Apache
> work.  While there are other users, I believe that Cocoon is the only
> Apache one.

I'm another non-apache user..
-pete


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


RE: [RT] so...many...components...

Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Peter Donald wrote.
> 
> Berin Loritsch wrote:
> > Just an FYI, the Source Resolve code is used by Fortress 
> right now, so 
> > we do have reason to keep that one around for a while.
> 
> I am not saying it be axed I guess I am saying that it should 
> be moved to the place where the community is and thus where 
> it will be actively maintained and developed. Fortress could 
> still use the component regardless of where it is located.
> 
Yes, that's true. Now, I still think the idea of the source
resolving package is great and it'S a pitty that it is only
used in some other projects.
So, I personally would be very happy if it would stay here.
Moving it, e.g. to Cocoon is not a real option as this would
required changes of package names. And then I guess we would
simply integrate the mechanism into the Cocoon core without
making a separate package.

> > XMLUtil is another beast entirely.  Apparently it is very 
> important to 
> > Cocoon, and I believe Carsten Zeigler used it in some other 
> non-Apache 
> > work.  While there are other users, I believe that Cocoon 
> is the only 
> > Apache one.
> 
>  From this and PeterRs comments I suspect this is one 
> component that may benefit from staying at Excalibur.
> 
+1

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Re: [RT] so...many...components...

Posted by Peter Donald <pe...@realityforge.org>.
Hi,

Berin Loritsch wrote:
> Just an FYI, the Source Resolve code is used by Fortress right now, so
> we do have reason to keep that one around for a while.

I am not saying it be axed I guess I am saying that it 
should be moved to the place where the community is and thus 
where it will be actively maintained and developed. Fortress 
could still use the component regardless of where it is located.

> XMLUtil is another beast entirely.  Apparently it is very important to
> Cocoon, and I believe Carsten Zeigler used it in some other non-Apache
> work.  While there are other users, I believe that Cocoon is the only
> Apache one.

 From this and PeterRs comments I suspect this is one 
component that may benefit from staying at Excalibur.

--
Cheers,

Peter Donald
*------------------------------------------------------*
| An expert is someone who knows everything about the  |
| topic except for its place in the world.             |
*------------------------------------------------------*

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Re: [RT] so...many...components...

Posted by Berin Loritsch <bl...@d-haven.org>.
Peter Donald wrote:
> 
> By "non-excalibur-community" I mean things like xmlutil, store and/or 
> sourceresolve. I haven't been active around here for ages but when I was 
> these were mainly (only?) maintained by Cocoon people. In the long term 
> it would seem to make sense that you move the code to where more 
> interested parties are likely to work on it (ie back into cocoon). The 
> fact that cocooners had (or still have?) access to excaliburs repo did 
> not make them a part of this community and IIRC there was no real 
> infusion of development energy.

Just an FYI, the Source Resolve code is used by Fortress right now, so
we do have reason to keep that one around for a while.

Store is a Cocoon brain child, and it very well may be replaced with
something newer.  Stefano has come up with an interesting idea about
an in-JVM cache that has some promise, but it is mathematically
complex to understand.  I don't know when "eventually" will come.

XMLUtil is another beast entirely.  Apparently it is very important to
Cocoon, and I believe Carsten Zeigler used it in some other non-Apache
work.  While there are other users, I believe that Cocoon is the only
Apache one.

-- 

"Programming today is a race between software engineers striving to 
build bigger and better idiot-proof programs, and the Universe trying to 
produce bigger and better idiots. So far, the Universe is winning."
                 - Rich Cook

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/


Re: [RT] so...many...components...

Posted by Peter Donald <pe...@realityforge.org>.
Hi,

Maybe it would be best to look at this from another 
perspective. There is only so much energy people can 
contribute to this project and there is significant chunk of 
"dead" code and/or non-excalibur-community code that is 
sucking energy away from the real work.

By "dead" code I mean stuff that was either forked out and 
is no longer actively developed, maintained and in some 
cases used. In these cases I think it makes sense to zap it 
from our repo and either archive it somewhere (if it is 
unused) or point users at replacement code (if it was forked).

* compatibility
         ==> commons-collections, spice-salt,
             doug leas concrrent, spice-jndikit,
             commons-cli
* configuration
         ==> spice-configkit for validation
         ... nuke the rest as it is unused?????
* event
         ==> d_haven-event
* i18n
         ==> spice-salt

By "non-excalibur-community" I mean things like xmlutil, 
store and/or sourceresolve. I haven't been active around 
here for ages but when I was these were mainly (only?) 
maintained by Cocoon people. In the long term it would seem 
to make sense that you move the code to where more 
interested parties are likely to work on it (ie back into 
cocoon). The fact that cocooners had (or still have?) access 
to excaliburs repo did not make them a part of this 
community and IIRC there was no real infusion of development 
energy.

As for the rest of the code I think it is important to 
determine exactly where it is used and what can be done to 
minimize the maintanence and/or development overhead.

Rather than doing it all in one shot lets take little steps 
and evolve the codebase incrementally.

--
Cheers,

Peter Donald
"Now, now my good man, this is no time for
making enemies." - Voltaire (1694-1778) on
his deathbed in response to a priest asking
that he renounce Satan.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Apache Excalibur Project -- URL: http://excalibur.apache.org/