You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2007/10/08 15:54:36 UTC

Apache Composer Proposal

I am watching http://wiki.apache.org/incubator/ComposerProposal with some
interest.  A couple of items:

  1) JAMES uses Phoenix, which is the old name for Plexus
  2) What about Apache Excalibur, currently home to the various
     Avalon modules (framework, components, etc.)?

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Apache Composer Proposal

Posted by Jason van Zyl <ja...@maven.org>.
There didn't seem to be any curfuffle at all in floating the proposal  
through the incubator. That's a good thing. Both containers are  
heavily used, both originate from these parts and so it's somewhat  
fitting they would like to return. I'll put up vote thread later today.

On 8 Oct 07, at 9:54 AM 8 Oct 07, peter royal wrote:

> On Oct 8, 2007, at 6:54 AM, Noel J. Bergman wrote:
>> I am watching http://wiki.apache.org/incubator/ComposerProposal  
>> with some
>> interest.  A couple of items:
>>
>>   1) JAMES uses Phoenix, which is the old name for Plexus
>
> yes, Loom was unsuccessful Phoenix fork. iirc, Plexus borrowed  
> concepts from Fortress more, but was mostly an independent  
> implementation
>
>>   2) What about Apache Excalibur, currently home to the various
>>      Avalon modules (framework, components, etc.)?
>
> Excalibur can continue on as-is.. iirc, Excalibur had made  
> movements to have some of its components be framework agnostic? If  
> so, they'd run in Composer. (the Composer component model is likely  
> going to be very much like pico's, which just runs with pojo's)
>
> -pete
>
>
> -- 
> proyal@apache.org - http://fotap.org/~osi
>
>
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------




---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Apache Composer Proposal

Posted by peter royal <pr...@apache.org>.
On Oct 8, 2007, at 6:54 AM, Noel J. Bergman wrote:
> I am watching http://wiki.apache.org/incubator/ComposerProposal  
> with some
> interest.  A couple of items:
>
>   1) JAMES uses Phoenix, which is the old name for Plexus

yes, Loom was unsuccessful Phoenix fork. iirc, Plexus borrowed  
concepts from Fortress more, but was mostly an independent  
implementation

>   2) What about Apache Excalibur, currently home to the various
>      Avalon modules (framework, components, etc.)?

Excalibur can continue on as-is.. iirc, Excalibur had made movements  
to have some of its components be framework agnostic? If so, they'd  
run in Composer. (the Composer component model is likely going to be  
very much like pico's, which just runs with pojo's)

-pete


-- 
proyal@apache.org - http://fotap.org/~osi




RE: Apache Composer Proposal

Posted by "Noel J. Bergman" <no...@devtech.com>.
> 1) JAMES uses Phoenix, which is the old name for Plexus

Actually, IIRC, Loom is Phoenix.  Hard to keep all of these Avalon
byproducts straight.  ;-)

	--- Noel



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org