You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Quinton McCombs <qm...@nequalsone.com> on 2003/04/28 20:24:41 UTC
[VOTE] Location of Avalon based services
I have been talking to Jason about the Avalonization of the Fulcrum
services. I had intended to take the code that is in Plexus (already
Avalonized), apply the changes made to the coupled services, and then
update the Fulcrum CVS repository. Jason has suggested that I just
apply the changes that have been made to the coupled services to what is
the plexus cvs repository and then we just use that code. This bring up
the obvious question on if we want to maintain the Avalonized services
in Apache's CVS or the plexus CVS.
So, use the plexus version
Or
Move the code into the Fulcrum repo?
--------------------------------------------
Quinton McCombs
NequalsOne - HealthCare marketing tools
mailto:qmccombs@NequalsOne.com
http://www.NequalsOne.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [VOTE] Location of Avalon based services
Posted by Jason van Zyl <ja...@zenplex.com>.
On Tue, 2003-04-29 at 05:33, Henning P. Schmiedehausen wrote:
> "Quinton McCombs" <qm...@nequalsone.com> writes:
>
> >the obvious question on if we want to maintain the Avalonized services
> >in Apache's CVS or the plexus CVS.
>
> That's IMHO pretty simple to answer (for me):
>
> Turbine is an Apache project. Plexus isn't. Turbine, as an Apache
> project has some sort of charter and framework. Plexus is Jasons'
> brain-child and while he says that he is pretty liberal in giving CVS
> access, there is not much visible yet beyond that. Plexus is pushed
> ahead by Jason and people who work with Jason. Jason took Plexus and
> Summit deliberatly off-Apache because he liked it that way.
>
> BTW: I'd like to get clarification on one issue. Jason can you help
> here?: Plexus is an Avalon container.
Plexus is a framework for making containers, the Avalon API is the first
implementation. So it behaves as an Avalon container old ECM components
or the new Avalon flavor components will work.
> In this it is simlar to ECM,
> Fortress, Phoenix, isn't it?
ECM, Fortress, Merlin and Phoenix are all containers of some flavour or
another. The focus of Plexus is runtime configurability, long-term
evolution and integration with Maven.
> Summit is the Avalon based, Turbine
> derived framework engine, which runs in the Plexus container. So
> shouldn't this be a "summit repository"?
Summit is really just an assembly of various components. Summit is a
composite component so the components that are currently used in Summit
will probably just be split out. The people can mix and match as they
see fit. Summit will really be a set of default components that are
useful. Some of the components are web specific but I don't think they
need to be separated. Someone might take some of the components in
Summit, make a couple of their own components and roll their own
framework. I'm more interested in adaptability and being able to quickly
satisfy requirements more than component reuse. People can obviously use
existing components but to me what's more important is providing the
infrastructure where people can assemble what they require, be able to
specialize quickly and not be burdened by massive APIs.
> Regards
> Henning
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Component repo (was: RE: [VOTE] Location of Avalon based services)
Posted by Quinton McCombs <qm...@nequalsone.com>.
> -----Original Message-----
> From: Henning P. Schmiedehausen [mailto:hps@intermeta.de]
> Sent: Tuesday, April 29, 2003 4:34 AM
> To: turbine-dev@jakarta.apache.org
> Subject: Re: [VOTE] Location of Avalon based services
>
>
> "Quinton McCombs" <qm...@nequalsone.com> writes:
>
> >the obvious question on if we want to maintain the
> Avalonized services
> >in Apache's CVS or the plexus CVS.
>
> That's IMHO pretty simple to answer (for me):
>
> Turbine is an Apache project. Plexus isn't. Turbine, as an
> Apache project has some sort of charter and framework. Plexus
> is Jasons' brain-child and while he says that he is pretty
> liberal in giving CVS access, there is not much visible yet
> beyond that. Plexus is pushed ahead by Jason and people who
> work with Jason. Jason took Plexus and Summit deliberatly
> off-Apache because he liked it that way.
>
> BTW: I'd like to get clarification on one issue. Jason can you help
> here?: Plexus is an Avalon container. In this it is simlar to
> ECM, Fortress, Phoenix, isn't it? Summit is the Avalon based,
> Turbine derived framework engine, which runs in the Plexus
> container. So shouldn't this be a "summit repository"?
>
> So to me the votes are:
>
> >So, use the plexus version
>
> -1
>
> >Or
>
> >Move the code into the Fulcrum repo?
>
> 0
>
> Personally, I'd like to see working, avalonized components
> being broken out and moved into a (like proposed on the
> commons-dev list) avalon-commons repository.
>
> There is not much sense in keeping code which is intended to
> be used in many different avalonized projects in a single
> project-repository. That's what the "commons" sites are for.
>
I would agree with this. For now, I think that we should use Fulcrum
for for the components until a more suitable location can be found.
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [VOTE] Location of Avalon based services
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Quinton McCombs" <qm...@nequalsone.com> writes:
>the obvious question on if we want to maintain the Avalonized services
>in Apache's CVS or the plexus CVS.
That's IMHO pretty simple to answer (for me):
Turbine is an Apache project. Plexus isn't. Turbine, as an Apache
project has some sort of charter and framework. Plexus is Jasons'
brain-child and while he says that he is pretty liberal in giving CVS
access, there is not much visible yet beyond that. Plexus is pushed
ahead by Jason and people who work with Jason. Jason took Plexus and
Summit deliberatly off-Apache because he liked it that way.
BTW: I'd like to get clarification on one issue. Jason can you help
here?: Plexus is an Avalon container. In this it is simlar to ECM,
Fortress, Phoenix, isn't it? Summit is the Avalon based, Turbine
derived framework engine, which runs in the Plexus container. So
shouldn't this be a "summit repository"?
So to me the votes are:
>So, use the plexus version
-1
>Or
>Move the code into the Fulcrum repo?
0
Personally, I'd like to see working, avalonized components being
broken out and moved into a (like proposed on the commons-dev list)
avalon-commons repository.
There is not much sense in keeping code which is intended to be used
in many different avalonized projects in a single
project-repository. That's what the "commons" sites are for.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org