Transitioning from Apple extensions

Mario Torre neugens.limasoftware at gmail.com
Fri Jun 1 01:07:36 PDT 2012


2012/6/1 Chris Harshman <harshman+javadev at gmail.com>:
> On Wed, May 30, 2012 at 4:29 AM, Artem Ananiev <artem.ananiev at oracle.com>wrote:
>
>> We at Oracle do our best to support all Java apps on Mac OS X that were
>> written for Apple's JDK6 and relied on Apple's extensions (system
>> properties, command line args, com.apple classes, etc.), but we don't
>> provide any official support for anything except public APIs.
>>
>
> Is there any sort of guide (official or otherwise) mapping Apple's
> extensions to public API replacement/equivalent/work-arounds? (I.e., is
> there a way current developers can hedge their bets, coding to the 'rich'
> Apple JDK6 experience but also degrading as gracefully as possible for
> OpenJDK 7+?)

That's the bet that people lose when use proprietary extensions.

What are the specific "features" you're missing? Perhaps the most
popular ones will be reintroduced, but I doubt that Apple specific
functionality will end in the main JDK, that's not the place for it.

Cheers,
Mario
-- 
pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF
Fingerprint: BA39 9666 94EC 8B73 27FA  FC7C 4086 63E3 80F2 40CF

IcedRobot: www.icedrobot.org
Proud GNU Classpath developer: http://www.classpath.org/
Read About us at: http://planet.classpath.org
OpenJDK: http://openjdk.java.net/projects/caciocavallo/

Please, support open standards:
http://endsoftpatents.org/


More information about the macosx-port-dev mailing list