You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by mp...@marmot.at on 2001/06/26 16:04:27 UTC
[vote]using torque generated om/peer classes
i would like to check in my changes to the security system:
(/proposals/sec)
* om/peer classes are torque generated
* SecurityEntitiy (interface) is used instead of SecurityObject (abstract class)
* om classes implement SecurityEntity, Comparable
* TurbineMapBuilder is no longer used (MapBuilders are generated)
martin
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [vote]using torque generated om/peer classes
Posted by Rafal Krzewski <Ra...@e-point.pl>.
Jason van Zyl wrote:
> On 6/26/01 10:04 AM, "mpoeschl@marmot.at" <mp...@marmot.at> wrote:
>
> > i would like to check in my changes to the security system:
> > (/proposals/sec)
> >
> > * om/peer classes are torque generated
> > * SecurityEntitiy (interface) is used instead of SecurityObject (abstract
> > class)
> > * om classes implement SecurityEntity, Comparable
> > * TurbineMapBuilder is no longer used (MapBuilders are generated)
> >
> > martin
>
> I'm +1 on the method but where are we going to put these changes?
+1
> They will first go in HEAD, but do we want to back port them
> to 2.1. I would prefer if we didn't as this would give people
> a big incentive to move forward and I'm worried about the
> maintenance problem between the proposal for for security
> in 2.2 and what people are using in 2.1.
2.1 should receive only bugfixes. I think that backporting every
new feature to past releases is a waste of effort. 2.1 is for supporting
pepople who already have applications, and would like to fix any
security holes or take benefit of performance improvements by simply
dropping 2.1.<minor> jars into their WEB-INF/lib.
New cool features should go into 2.2, and people must decide for
themselves
when they want to switch. (setting a -pre tag on the HEAD is probably
the
right moment to begin evaluating the new version).
> If we moved quickly to get an alpha of 2.2 out in a couple
> of weeks could we keep these changes for 2.2 and forget about
> back porting them?. I know the changes are pretty much backward compatible
> but it's quite a radical change from what's in 2.1 now.
That's good. 2.2 is supposed to be radicaly better than 2.1, right?
Rafal
--
mgr inz. Rafal Krzewski
Senior Internet Developer
mailto:Rafal.Krzewski@e-point.pl
+48 22 8534830 http://e-point.pl
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [vote]using torque generated om/peer classes
Posted by Jason van Zyl <jv...@apache.org>.
On 6/26/01 10:04 AM, "mpoeschl@marmot.at" <mp...@marmot.at> wrote:
> i would like to check in my changes to the security system:
> (/proposals/sec)
>
> * om/peer classes are torque generated
> * SecurityEntitiy (interface) is used instead of SecurityObject (abstract
> class)
> * om classes implement SecurityEntity, Comparable
> * TurbineMapBuilder is no longer used (MapBuilders are generated)
>
> martin
I'm +1 on the method but where are we going to put these changes?
They will first go in HEAD, but do we want to back port them
to 2.1. I would prefer if we didn't as this would give people
a big incentive to move forward and I'm worried about the
maintenance problem between the proposal for for security
in 2.2 and what people are using in 2.1.
If we moved quickly to get an alpha of 2.2 out in a couple
of weeks could we keep these changes for 2.2 and forget about
back porting them?. I know the changes are pretty much backward compatible
but it's quite a radical change from what's in 2.1 now.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org