You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by "Courcoux Peter, Slough" <Pe...@anite.com> on 2004/11/29 15:59:35 UTC

RE: cvs commit: jakarta-turbine-2/src/test/org/apache/turbine/ser vices/avaloncomponent MerlinComponentServiceTest.java

I'm working with both Turbine 2.4 and metro, but not with metro and Turbine
together (yet), I will definitely be interested in using metro with turbine
and with the fulcrum components.

Regards,

Peter

-----Original Message-----
From: Niclas Hedhman [mailto:niclas@hedhman.org] 
Sent: 29 November 2004 14:55
To: Turbine Developers List
Subject: Re: cvs commit:
jakarta-turbine-2/src/test/org/apache/turbine/services/avaloncomponent
MerlinComponentServiceTest.java

On Monday 29 November 2004 22:25, Henning P. Schmiedehausen wrote:

> IMHO, the Excalibur / Metro code will pretty soon diverge because of
> the chemistry of the developers...

Yes. Excalibur is not moving much, and Metro is breaking new ground. 
Definately divergence in progress.
The Metro folks were a bit surprised to see Eric's statement, and honestly 
don't expect Turbine to follow into our ventures. If Turbine/Fulcrum stays 
compatible with 'Excalibur' (whatever that means), I think it is our job to 
make Turbine and Fulcrum components working in Metro, if we choose to do so.


Cheers
Niclas
-- 
   +------//-------------------+
  / http://www.dpml.net       /
 / http://niclas.hedhman.org / 
+------//-------------------+


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


Scanned for viruses by MessageLabs


Scanned for viruses by MessageLabs. The integrity and security of this message cannot be guaranteed. This email is intended for the named recipient only, and may contain confidential information and proprietary material. Any unauthorised use or disclosure is prohibited.

RE: cvs commit: jakarta-turbine-2/src/test/org/apache/turbine/services/avaloncomponent MerlinComponentServiceTest.java

Posted by Eric Pugh <ep...@upstate.com>.
I think it all just boils down to interest.  If folks are using Metro and
are willing to support it as a container under Turbine, great.
Theoretically it's just a matter of providing a bit of glue and off it
goes...  Hence the /extensions directory for things like this.

One of my goals for Turbine 2.4 is to cut down on the number of unreleased
jars we are dependendent on.  Commons Email, configuration, etc.  Removing
the Merlin stuff for now until Metro reaches a 1.0 is just part of that
process.  It's been an ongoing problem in the past, and adding support for
new things that don't have releases just isn't a good idea from the
perspective of maintainablility.

Eric

> -----Original Message-----
> From: Courcoux Peter, Slough [mailto:Peter.Courcoux@anite.com]
> Sent: Monday, November 29, 2004 4:00 PM
> To: 'Turbine Developers List'
> Subject: RE: cvs commit:
> jakarta-turbine-2/src/test/org/apache/turbine/services/avaloncomponent
> MerlinComponentServiceTest.java
>
>
> I'm working with both Turbine 2.4 and metro, but not with metro and
> Turbine
> together (yet), I will definitely be interested in using metro with
> turbine
> and with the fulcrum components.
>
> Regards,
>
> Peter
>
> -----Original Message-----
> From: Niclas Hedhman [mailto:niclas@hedhman.org]
> Sent: 29 November 2004 14:55
> To: Turbine Developers List
> Subject: Re: cvs commit:
> jakarta-turbine-2/src/test/org/apache/turbine/services/avaloncomponent
> MerlinComponentServiceTest.java
>
> On Monday 29 November 2004 22:25, Henning P. Schmiedehausen wrote:
>
> > IMHO, the Excalibur / Metro code will pretty soon diverge because of
> > the chemistry of the developers...
>
> Yes. Excalibur is not moving much, and Metro is breaking new ground.
> Definately divergence in progress.
> The Metro folks were a bit surprised to see Eric's statement, and
> honestly
> don't expect Turbine to follow into our ventures. If Turbine/Fulcrum
> stays
> compatible with 'Excalibur' (whatever that means), I think it is our job
> to
> make Turbine and Fulcrum components working in Metro, if we choose to do
> so.
>
>
> Cheers
> Niclas
> --
>    +------//-------------------+
>   / http://www.dpml.net       /
>  / http://niclas.hedhman.org /
> +------//-------------------+
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
>
> Scanned for viruses by MessageLabs
>
>
> Scanned for viruses by MessageLabs. The integrity and security of this
> message cannot be guaranteed. This email is intended for the named
> recipient only, and may contain confidential information and proprietary
> material. Any unauthorised use or disclosure is prohibited.
>


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