move from fulcrum to turbine-components [was: Torque 3.1 Status?]

[Martin Poeschl <mp...@marmot.at>]

we talked about using the (existing but unused) turbine-component 
repository for the new avalon components instead of fulcrum .. and also 
change the package name ... but it was just an idea .. we should discuss 
it on the turbine-dev list (so i'll send a copy)

martin

Eric Pugh wrote:

>Thanks Martin,
>
>Mucking around in PRE_AVALON_BRANCH etc seems rather challenging, and I
>appreciate your doing it.  As a follow on though, I am getting closer and
>closer to cutting some 1.0 releases for some of the components in Fulcurm
>CVS HEAD.
>
>Assuming we have the MerlinComponentService integrated into Scarab nicely,
>then, without converting ALL the fulcrum code at once, how can we set it up
>so that the code in the fulcrum.jar from the PRE_AVALON_BRANCH for say
>org.apache.fulcrum.mimetype.MimeTypeService doesn't get used, and instead
>the Merlinized Fulcrum version of MimeTypeService is loaded.  I guess we
>could delete the classes from the fulcrum.jar file so that it picks up the
>onces in the fulcrum-mimetype-api.jar file...?   Also, I am hoping that
>since Merlin has it's own big classloader/container seperation magic, that
>it won't be an issue b/c of that.  At any rate, just interested in your
>thoughts..
>
>Eric
>
>
>  
>



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

RE: move from fulcrum to turbine-components [was: Torque 3.1 Status?]

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

There is a Turbine Components repository!!??  LOL, the things you learn..
And here I have been sticking stuff in the \extensions directory because I
didn't want them tightly coupled to turbine, but still part of turbine!

I think using a turbine-component repository makes sense if the criteria to
have access are different/lower from the criteria for accessing
jakarta-turbine-2.  Otherwise, to me, it just seems like yet another project
and cvs to deal with.  However, I am not real gungho one way or the other.

As far as the fulcrum repo, I wouldn't be too keen on moving the existing
components over to turbine-component after all the effort to rework them
etc.  However, I do think that if a component is turbine specific then it
should NOT be in fulcrum.  I think components in fulcrum should be
relatively selfcontainer and reusable in multiple environments, not just
Turbine.  If you have a component that is turbine specific, then it should
go in the aforementioned turbine-components repo or the /extensions repo.

However, that doesn't mean that a code that ties into Turbine automatically
can't go into Fulcrum.  For instance, the fulcrum-security code has adapters
for OSUSer as well as Turbine Users.  I think that could maybe all stay
together.  I guess it mostly depends on what keeps the build the easiest and
has the best setup of commit priviliges for the developers involved.

Eric



> -----Original Message-----
> From: Martin Poeschl [mailto:mpoeschl@marmot.at]
> Sent: Saturday, November 22, 2003 2:13 PM
> To: dev@scarab.tigris.org; Turbine Developers List
> Subject: move from fulcrum to turbine-components [was: Torque 3.1
> Status?]
>
>
> we talked about using the (existing but unused) turbine-component
> repository for the new avalon components instead of fulcrum
> .. and also
> change the package name ... but it was just an idea .. we
> should discuss
> it on the turbine-dev list (so i'll send a copy)
>
> martin
>
> Eric Pugh wrote:
>
> >Thanks Martin,
> >
> >Mucking around in PRE_AVALON_BRANCH etc seems rather
> challenging, and I
> >appreciate your doing it.  As a follow on though, I am
> getting closer and
> >closer to cutting some 1.0 releases for some of the
> components in Fulcurm
> >CVS HEAD.
> >
> >Assuming we have the MerlinComponentService integrated into
> Scarab nicely,
> >then, without converting ALL the fulcrum code at once, how
> can we set it up
> >so that the code in the fulcrum.jar from the
> PRE_AVALON_BRANCH for say
> >org.apache.fulcrum.mimetype.MimeTypeService doesn't get
> used, and instead
> >the Merlinized Fulcrum version of MimeTypeService is loaded.
>  I guess we
> >could delete the classes from the fulcrum.jar file so that
> it picks up the
> >onces in the fulcrum-mimetype-api.jar file...?   Also, I am
> hoping that
> >since Merlin has it's own big classloader/container
> seperation magic, that
> >it won't be an issue b/c of that.  At any rate, just
> interested in your
> >thoughts..
> >
> >Eric
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@scarab.tigris.org
> For additional commands, e-mail: dev-help@scarab.tigris.org


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