harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Loenko, Mikhail Y" <mikhail.y.loe...@intel.com>
Subject RE: [RESULT] ( Was Re: [VOTE] Accept JIRA contribution HARMONY-16 (Intel's contrib of security code for classlib))
Date Tue, 10 Jan 2006 08:52:56 GMT
Thanks for accepting the contribution

>There's a bit of things that come out of this, like the
>"com.intel.drl.spec_ref" javadoc tag that we should convert, and such.

What would be the best for those javadocs? We can have 3 possible
options:
1. Copy-paste from the spec. Not sure it is legal
2. Reword the spec. More likely to be legal
3. Replace the tag with a different one and provide taglet to build the
doc from the Harmony sources and Sun's spec.

Currently IBM's contribution seems to have #2. Does anyone have an
opinion?

Thanks,
Mikhail Loenko
Intel Middleware Products Division

>-----Original Message-----
>From: Geir Magnusson Jr [mailto:geir@pobox.com]
>Sent: Friday, December 30, 2005 10:48 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [RESULT] ( Was Re: [VOTE] Accept JIRA contribution
HARMONY-16 (Intel's contrib of
>security code for classlib))
>
>
>
>Tim Ellison wrote:
>> Geir Magnusson Jr. wrote:
>> <snip>
>>
>>>I'll finish moving to SVN and we'll put into the classlib tree, I
suppose.
>>
>>
>> Great.  Thanks again Mikhail and the team!
>>
>> I suggest you either put it into the classlib tree at
>> "classlib/java-src/security2" or leave it in the sandbox, then we can
>> merge it into the existing security structure without breaking the
world.
>
>I'll go for the former and try to whip it into common shape, and we can
>then decide how we do this - drop the existing security if security2 is
>a superset, or merge.
>
>There's a bit of things that come out of this, like the
>"com.intel.drl.spec_ref" javadoc tag that we should convert, and such.
>
>Also will give me a good change to frame out the test infra.
>
>
>>
>> Regards,
>> Tim
>>

Mime
View raw message