I have requested Rhino 1.6R5 for you from
Eclipse Legal. That item is still open. It is also the case that Eclipse Legal
is very backed up in their review
process so for some of the open items, I have been double checking to see if a
previously approved version can “work” for Higgins 1.0. In some cases the answer has been yes,
and in other cases the answer has been no.
It sounds like it doesn’t make sense
to fall back to Rhino 1.6R2 even for the short term. So I will get back to Eclipse legal
saying that we need 1.6R5 for Higgins 1.0.
Unfortunately it can take a very long time
to get approvals, especially for programs that have not been previously
approved in any version. For example, the CQ for the base Jena code
was entered last fall, and Jena itself
is still not approved. (It has been
working its way through the process.)
So yes, after we get past Higgins 1.0, all
the component owners should anticipate their third party dependencies for the
next release so that we can get items in the queue as early as possible.
higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Duane Buss
Sent: Tuesday, August 07, 2007
To: 'Higgins (Trust Framework)
Project developer discussions'
Subject: RE: [higgins-dev] Can the
JNDI context provider use Rhino1.6.1or 1.6.2 rather than 1.6.5?
Mary are you asking that we
temporary state we can use 1.6R1 or 1.6R2 until legal catches up or are you
asking us to move back to these crusty versions and remove 1.6R5 from the
eclipse legal queue so we can reduce their workload? In
general with all of the updates we have been discussing I hope we aren't
accepting the old versions of dependancies and then removing the newer versions
During testing months ago the
scripts we were using didn't work with 1.6R2 of Rhino, and
were not fully reported. Rhino 1.6R2 is old, dating from 2005-09-19
and missing the following bug
fixes to get to 1.6R3. 1.6R4 was a single bug fix ,
and 1.6R5 was updating the code to the mozilla
tri-license. As of the end of July Rhino download
links have changed and 1.6.5 is now considered old and must be accessed from
the download archives with 1.6R6 being the new preferred supported
It won't be long before we
we can call back into java var arg functions (audit and logging), better
warning and error messages to simplify debugging, fewer external dependancies,
bug fixes. If this is a multi year process to get approved then
I may want to start it now anticipating that I might use it.
"Mary Ruddy" <mary@xxxxxxxxxxxxxxxxx>
"'Higgins (Trust Framework) Project developer
7/31/2007 1:16 PM
RE: [higgins-dev] Can the JNDI context provider use
Rhino1.6.1 or 1.6.2 rather than 1.6.5?
When Eclipse wrote 1.6.2 they meant 1.6R2 (CQ 78 for approval of 1.6.2
references the 1.6R2 code.) Let me know if 1.6R2 (or 1.6R1)works.
[mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Tom Doman
Sent: Tuesday, July 31, 2007 11:21 AM
To: 'Higgins (Trust Framework) Project developer discussions'
Subject: Re: [higgins-dev] Can the JNDI context provider use Rhino1.6.1
or 1.6.2 rather than 1.6.5?
I still have the same "." vs. "R" question I outlined here
they interchangeable? ie. 1.6R5 == 1.6.5. As I described before,
download site (http://www.mozilla.org/rhino/download.html) uses "R".
>>> "Mary Ruddy" <mary@xxxxxxxxxxxxxxxxx> 7/24/2007
9:49 AM >>>
Because of the backlog of code that needs to be reviewed for Higgins by
Eclipse legal, we need to maximize reuse (use versions that have already
been approved). Rhino 1.6.1 and 1.6.2 have already been approved.
Please verify that one of these works for you or that you could make it
higgins-dev mailing list
higgins-dev mailing list