So someone will make all the necessary OS X source and build changes in
this new
7ux forest to build something that if it runs at all, certainly won't
run client apps ?
It might be enough for running the non-client tests but it seems like
that's the
kind of dead end changes that are better made in some other forest
rather than
the one that's supposed to host the "real" work.
-phil.
On 10/25/2011 1:05 PM, Paul Hohensee wrote:
Yes, I think we knew that. What I was proposing was an interim state of
jdk7u-osx (call it the Oracle forest: jdk7u-osx is quite a mouthful)
where
we could build testable bundles on osx before the client work is
integrated.
Paul
On 10/25/11 3:46 PM, Phil Race wrote:
Paul,
Just so you know, OpenJDK on OS X doesn't use X11.
Earlier that's all there was but now that's obsolete and its based on
Cocoa APIs.
-phil.
On 10/19/11 12:27 PM, Paul Hohensee wrote:
On 10/17/11 4:20 PM, Henri Gomez wrote:
What does it means for osx builder like me ?
This is what I expect, actual process may vary a bit.
The forest is a development forest, so while you ought to be able to
build it at any given time, it's not necessarily completely stable
(i.e.,
may not pass the jcks at any given time). Until we get the
infrastructure in place to build an X11-based bundle that runs on OS X,
it won't be very useful. That'll be pretty much all makefile changes.
Once we have that plus hotspot (which we already have in
hsx/hotspot-rt),
everyone except the client team (i.e., graphics team) will be able
to build
and test on OS X under X11.
When could we try to use it for OS/X builds ?
When we get the infrastructure for building on OS X done, vis. above.
Paul
2011/10/17 Paul Hohensee<[email protected]>:
Thanks, Dalibor.
The forest is here
http://hg.openjdk.java.net/jdk7u/jdk7u-osx/
and the corresponding gates here
http://hg.openjdk.java.net/jdk7u/jdk7u-osx-gate/
The jdk7u-osx forest is a clone of jdk7u/jdk7u-dev and has the
same jcheck
constraints as jdk7u-dev (i.e., duplicate bugids are allowed).
The push
notification
alias is
[email protected]
When component teams deem it advisable, they'll ask permission to
push to
jdk7u-dev via the existing process.
Hotspot pushes to jdk7u-osx will likely happen on the same
schedule as those
to jdk7u-dev. The initial port is wending its way through the
integration
process
from hsx/hotspot-rt through hsx/hotspot-main to hsx/hsx23, and
will go from
there to jdk7u-osx/hotspot.
Paul
On 10/11/11 8:59 AM, Dalibor Topic wrote:
On 10/6/11 6:37 PM, Dalibor Topic wrote:
On 10/6/11 8:16 AM, Paul Hohensee wrote:
At JavaOne, Oracle announced the developer preview of the JDK7
Mac OSX
port. Apple is open-sourcing the port and Oracle plans to
deliver it in
a future JDK7 update release. Since the initial port will use
the JDK7
code
base, I'd like to propose the creation of a project repo forest
for the
port
as a sub-project of the JDK7 update project. Once a stable port
exists
in the OSX project repo forest, we can request permission to
push it to
jdk7u.
Thanks for this proposal, Paul.
I posted a link to the Oracle JDK 7 Update release roadmap
published at
JavaOne
and the corresponding press releases which give some more
background
information
on the plans wrt to the Mac OS X port to provide some more
background for
this
request. [1]
I'd like to open up this proposal for discussion until Monday.
Thanks to everyone who participated in the discussion. With my JDK 7
Updates Project
Lead hat on, I think this is a good proposal, so we will go ahead
and
create a separate
jdk7u-osx forest for the jdk7u integration of the Mac OS X port
based off
the mainline
jdk7u master, with commit e-mails heading to the macosx-port-dev
list in
order to
keep the Mac porters up to date on the progress of jdk7u(4)
integration
work.
cheers,
dalibor topic
cheers,
dalibor topic
[1]
http://mail.openjdk.java.net/pipermail/jdk7u-dev/2011-October/000534.html
