Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365900 - Update to Rhino (org.mozilla.javascript) 1.7R3 (aka 1.7.3)
Summary: Update to Rhino (org.mozilla.javascript) 1.7R3 (aka 1.7.3)
Status: RESOLVED WONTFIX
Alias: None
Product: Orbit
Classification: Tools
Component: bundles (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Andrew Overholt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 09:02 EST by Andrew Overholt CLA
Modified: 2012-09-10 15:48 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-12-07 09:02:07 EST 
Rhino 1.7R3 was released upstream on 2011-06-03.

http://www.mozilla.org/rhino/download.html

It has some API changes that affect BIRT (see bug 351482) but it's probably best to stay with upstream releases rather than peg ourselves to the older 1.7R2.  Some Linux distributions are moving ahead (Fedora is already at 1.7R3) and this is affecting their continued inclusion of BIRT.
Comment 1 Martin Oberhuber CLA 2011-12-07 09:09:02 EST 
So who's going to drive this and file the CQ ?
Comment 2 Andrew Overholt CLA 2011-12-07 10:13:13 EST 
I can do it but it'll be my first Orbit submission.
Comment 3 Chris Aniszczyk CLA 2011-12-07 11:18:01 EST 
I'll nominate you as an orbit committer if that's OK Andrew?
Comment 4 Martin Oberhuber CLA 2011-12-07 12:16:29 EST 
Do we know of a project that would be adopting / releasing this ? AFAIK we shouldn't put things into Orbit unless there's also a project picking it up ?
Comment 5 David Williams CLA 2011-12-07 12:52:29 EST 
(In reply to comment #4)
> Do we know of a project that would be adopting / releasing this ? AFAIK we
> shouldn't put things into Orbit unless there's also a project picking it up ?

I can confirm the steps, first an Eclipse Project needs a CQ saying they need it, then we have an Orbit CQ piggy back off that one (then any other project who needs it piggybacks on Orbit CQ).
Comment 6 Andrew Overholt CLA 2011-12-07 13:31:48 EST 
Yeah, let's wait on the dependent bug (bug 351482) before we open a CQ.

Sorry if one shouldn't open an Orbit bug before the dependent changes are finished; I just thought I'd associate the required BIRT bug and the Orbit bug.
Comment 7 David Williams CLA 2011-12-07 14:00:13 EST 
(In reply to comment #6)
> Yeah, let's wait on the dependent bug (bug 351482) before we open a CQ.
> 
> Sorry if one shouldn't open an Orbit bug before the dependent changes are
> finished; I just thought I'd associate the required BIRT bug and the Orbit bug.

Oh no apologies necessary! I was just talking about CQs ... this way, you've started the discussion on if you want to become an Orbit committer? :)
Comment 8 Chris Aniszczyk CLA 2011-12-07 14:04:38 EST 
I sent the nomination out for vote on orbit-dev, good luck getting rhino updated!
Comment 9 David Williams CLA 2012-09-10 15:34:55 EDT 
And now we already have Mozilla Rhino Version: 1.7R4 (bug 389187). 

Do we still need R3 if we have R4?
Comment 10 Andrew Overholt CLA 2012-09-10 15:48:34 EDT 
I'd like to see as few versions as possible (1, ideally) in Orbit so let's just go with R4 and skip R3.  Note that there's been no movement on the BIRT bug to update their Rhino dependency (bug 351482).