+1 to consolidating on a single security module. I'm also interested to hear what merging Mikhail has in mind.
I was led to believe that security2 was a proper superset of security, so we should be able to do a 'big bang' switch. The security_orig won't be too far away if we need to pull something in. (Perhaps move it out of trunk/modules/ to avoid confusion?) Regards, Tim Geir Magnusson Jr wrote: > Before you do that... > > What are you thinking as your approach? > > geir > > Mikhail Loenko wrote: >> I suggest merging these two bundles. I can do this and provide a patch... >> >> Thanks, >> Mikhail >> >> On 2/9/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote: >>> security classes are a subset of security2 classes. >>> >>> security2 is 1.5-ready while security has javadocs. What do you mean >>> by 'better'? >>> Are there any original approaches or efficient algorithms used in >>> security? >>> >>> Thanks, >>> Mikhail >>> >>> >>> On 2/9/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote: >>>> Hm. I thought security was stubs, but it isn't. >>>> >>>> Is there anything in security/ that we don't have in security2/ or is >>>> better? >>>> >>>> geir >>>> >>>> Geir Magnusson Jr wrote: >>>>> Unless I hear massive bellowing in opposition, I'm going to move >>>>> security -> security_orig and security2 -> security sometime tomorrow. >>>>> Please register protests now... >>>>> >>>>> geir >>>>> >>>>> >> >> > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK.
