what to do with excalibur???

[Leo Simons <le...@apache.org>]

(ringing the alarm bell here :D)


Hi gang!


I started on updated excalibur releases two-and-a-half weeks ago. Did 
the maven conversion, screwed up (still in the process of fixing) gump, 
built some candidates, sollicited help and feedback.

A little feedback came, but no help. Despite making every effort to make 
it easy to dig in and do the work.

Why is that? Doesn't anyone need or want these components? (cocoon, for 
example, was released on schedule, without them; seems they're fine with 
cvs snapshots)

I'm wondering whether I should just abort building these releases and 
save myself some work (no, I won't be using these packages myself, which 
was a warning sign I ignored, figuring I owe my share of "legacy support 
work").

Fact of life is that the only materials in active development in 
excalibur cvs are the components directly used by cocoon, and these are 
only developed actively when cocoon needs a change (or a bugfix).

It smells of potential code rot. As do the testcases, that have probably 
been failing for ages.

what do we do?


- LSD



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

Re: what to do with excalibur???

[Leo Simons <le...@apache.org>]

Leo Simons wrote:
> what do we do?

For those wondering...

...given the mild response to this and earlier e-mails about this stuff, 
I'm going to just let this slide off the radar until it starts itching.

- Leo



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

RE: what to do with excalibur???

[Eric Pugh <ep...@upstate.com>]

Because Excaliber is deprecated, I would move towards putting the efforts
towards what isn't deprecated.  Turbine has ECM support, but that is
deprecated, hence the lack of interest from that side on updated ECM.  I am
guessing since Fortress was a very simple upgrade, that most people have
moved on...?

>From the standpoint of cleanliness it is probably worth fixing things like
gump so that things that compile.  But the fact that the unit tests fail is
a good warning to people not to start projects with ECM.

Eric

> -----Original Message-----
> From: news [mailto:news@sea.gmane.org]On Behalf Of Leo Simons
> Sent: Monday, November 24, 2003 11:07 AM
> To: dev@avalon.apache.org
> Subject: what to do with excalibur???
>
>
> (ringing the alarm bell here :D)
>
>
> Hi gang!
>
>
> I started on updated excalibur releases two-and-a-half weeks ago. Did
> the maven conversion, screwed up (still in the process of
> fixing) gump,
> built some candidates, sollicited help and feedback.
>
> A little feedback came, but no help. Despite making every
> effort to make
> it easy to dig in and do the work.
>
> Why is that? Doesn't anyone need or want these components?
> (cocoon, for
> example, was released on schedule, without them; seems
> they're fine with
> cvs snapshots)
>
> I'm wondering whether I should just abort building these releases and
> save myself some work (no, I won't be using these packages
> myself, which
> was a warning sign I ignored, figuring I owe my share of
> "legacy support
> work").
>
> Fact of life is that the only materials in active development in
> excalibur cvs are the components directly used by cocoon, and
> these are
> only developed actively when cocoon needs a change (or a bugfix).
>
> It smells of potential code rot. As do the testcases, that
> have probably
> been failing for ages.
>
> what do we do?
>
>
> - LSD
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org