Status

Core Graveyard
Java: OJI
RESOLVED FIXED
11 years ago
7 years ago

People

(Reporter: Mark Mentovai, Assigned: Mark Mentovai)

Tracking

({fixed1.8.0.2, fixed1.8.1})

Trunk
PowerPC
Mac OS X
fixed1.8.0.2, fixed1.8.1
Bug Flags:
blocking1.8.1 +
blocking1.8.0.2 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nvn-dl])

Attachments

(1 attachment)

44 bytes, text/plain
Josh Aas
: review+
Mike Pinkerton (not reading bugmail)
: superreview+
Details
(Assignee)

Description

11 years ago
We need a universal JavaEmbeddingPlugin and MRJPluginJEP to accompany any universal product release.  Because the JEP exists in our tree in binary form, we can't rely on the new cross/universal build enhancements to produce a fat JEP, we need to check one in.

I've built fat JEP bits from 0.9.5+c source with the x86 compatibility patches in bug 315163 and bug 325084, and have shipped them with Camino 1.0.  Review and approval is needed to land these on the trunk, 1_8, and 1_8_0 branches.
(Assignee)

Updated

11 years ago
Flags: blocking1.8.1?
Flags: blocking1.8.0.2?
(Assignee)

Comment 1

11 years ago
Created attachment 212369 [details]
Fat JEP 0.9.5+c + x86 patches

I'm not going to chew up space by attaching the huge binary bits to this bug (they'd exceed the limit anyway).  The fat JEP I'm talking about already lives on CAMINO_1_0_BRANCH at mozilla/plugin/oji/JEP, you can also pick up the files (stripped of debugging symbols) from Camino 1.0 in Camino.app/Contents/MacOS/plugins.

This dummy file and the requests on it represent that fat JEP 0.9.5+c with patches from bug 315163 and bug 325084.
Attachment #212369 - Flags: superreview?(sfraser_bugs)
Attachment #212369 - Flags: review?(joshmoz)
Attachment #212369 - Flags: approval1.8.0.2?
Attachment #212369 - Flags: approval-branch-1.8.1?(joshmoz)
(Assignee)

Comment 2

11 years ago
(Steven doesn't have an x86 Mac yet, that's why these patches haven't been addressed in a JEP release, and why he hasn't released a fat JEP.)
Flags: blocking1.8.1?
Flags: blocking1.8.1+
Flags: blocking1.8.0.2?
Flags: blocking1.8.0.2+

Updated

11 years ago
Attachment #212369 - Flags: review?(joshmoz)
Attachment #212369 - Flags: review+
Attachment #212369 - Flags: approval-branch-1.8.1?(joshmoz)
Attachment #212369 - Flags: approval-branch-1.8.1+
Comment on attachment 212369 [details]
Fat JEP 0.9.5+c + x86 patches

approved for 1.8.0 branch, a=dveditz
Attachment #212369 - Flags: approval1.8.0.2? → approval1.8.0.2+
(Assignee)

Comment 4

11 years ago
smfr, needs sr.
Comment on attachment 212369 [details]
Fat JEP 0.9.5+c + x86 patches

sr=pink
Attachment #212369 - Flags: superreview?(sfraser_bugs) → superreview+
(Assignee)

Comment 6

11 years ago
Universal JEP 0.9.5+c checked in on the trunk.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Assignee)

Comment 7

11 years ago
Checked JEP 0.9.5+c universal + patches in on 1_8 and 1_8_0.
Keywords: fixed1.8.0.2, fixed1.8.1
(Assignee)

Comment 8

11 years ago
For reference, information on exactly what was checked in from the checkin message:

327785 Universal (fat) JEP. This is JEP 0.9.5+c. JavaEmbeddingPlugin.bundle was rebuilt for both architectures with patches from 315163 and 325084. MRJPlugin.plugin was rebuilt for x86 with patches from 315163. r=josh sr=pink a/1.8=josh a/1.8.0=dveditz
(Assignee)

Comment 9

11 years ago
Re-landed on both branches - I initially only landed 0.9.5+c without patches and without x86.

Updated

11 years ago
Whiteboard: [nvn-dl]
Last week I got my MacBook Pro, and today I've released a new version of the
JEP (0.9.5+d) whose binaries are "universal binaries"!

http://javaplugin.sourceforge.net/

I included all of Mark's Intel-specific changes (comment #0), though sometimes
I expanded them a bit (for example I'm now using Objective C "categories" for
all undocumented APIs, and not just to replace calls to objc_msgSend_stret()).

Thanks again, Mark, for making your own JEP universal binaries!  You took a
lot of pressure off of me, and you found out what needed to be done.

I don't know whether or not you guys want to go back to just putting JEP
binaries in the build tree, but that's up to you.
(Assignee)

Comment 11

11 years ago
(In reply to comment #10)
> I don't know whether or not you guys want to go back to just putting JEP
> binaries in the build tree, but that's up to you.

Yes, we do!

I kept having a recurring nightmare that you would release a new JEP version but it would still be PPC-only.

Updated

7 years ago
Component: Java: OJI → Java: OJI
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.