For the time being I'm going to assume we can do a release as long as we
follow the guidelines outlined by Geir. I'll ask over on legal-discuss to
see if anyone else has comments on this.

  ...ant

On 3/5/07, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:

OK :) .. what's the true status of releasing code that implements JCP
standards?

Sanjiva.

Geir Magnusson Jr. wrote:
> That's simply not true
>
> geir
>
> On Mar 4, 2007, at 10:19 PM, Sanjiva Weerawarana wrote:
>
>> My understanding is that if we include javax.* stuff then we have to
>> pass the TCK before we release. This was the reason that we separated
>> JCP API support from the core in Axis2.
>>
>> Sanjiva.
>>
>> ant elder wrote:
>>> Does anyone know if we're allowed to do a milestone or beta release
>>> of BSF
>>> v3 which includes the javax.script classes before it passes the
>>> JSR-223 TCK?
>>> Searching the email archives about this it wasn't clear if we may do a
>>> release long as we have a clear disclaimer saying we don't comply
>>> with the
>>> spec, or if we must not release anything which includes a javax.script
.
>>> class until we pass the TCK. Anyone know either way?
>>>   ...ant
>>
>> --Sanjiva Weerawarana, Ph.D.
>> Founder & Director; Lanka Software Foundation;
http://www.opensource.lk/
>> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> Director; Open Source Initiative; http://www.opensource.org/
>> Member; Apache Software Foundation; http://www.apache.org/
>> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
>

--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to