You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tim Ellison <t....@gmail.com> on 2010/10/27 11:18:24 UTC

[general] Harmony future roadmap

The Harmony PMC have had a brief discussion about the goals of the
Harmony project, based upon statements made in the last JCP face to face
meeting.  Now that the nature of those statements has become public
elsewhere [1], the 'Harmony goals' discussion can move onto the public
list here.

As you know, the current goal of Apache Harmony is a compatible and
*compliant* implementation of Java SE.  In the last JCP meeting Oracle
made a definitive statement regarding Apache's long-standing request for
a JCK license that is compatible with our desire to release Harmony
under ALv2.  The official version of the definitive statement will
eventually be reflected in the JCP meeting minutes, but the unofficial
version is that Oracle stated they will not offer the Java SE JCK
license we need to complete our goal.  It was clear that this is a final
decision from Oracle and that there are no further opportunities for
productive discussion on this topic.

This means that Harmony's current goal is unachievable.  However, we
have a wonderful resource in the code and contributors that have got us
to this point.  So the question is what happens from here?  What are the
new goals for Harmony that will move us on beyond this impasse?

I think all options and opinions are open for discussion.  We could
simply continue with the current goal and encourage the Apache Board to
seek the JCK license by whatever means is posible, we could modify our
goal and plan to release an uncertified Java SE runtime, or more
radically change Harmony's goal away from Java SE.  There are many options.

I'll just put the question out there at the moment, and save my own
opinions for a later post.

What do you see as the future roadmap for Apache Harmony?

[1] e.g. http://s.apache.org/xI

Regards,
Tim

Re: [general] Harmony future roadmap

Posted by ch...@k-embedded-java.com.
> In message <4C...@gmail.com>, Tim Ellison writes:
>> On 31/Oct/2010 20:23, chris.gray@k-embedded-java.com wrote:
>> >
>> > Tim Ellison wrote:
>> > >
>> > > I think all options and opinions are open for discussion.  We could
simply continue with the current goal and encourage the Apache
Board to seek the JCK license by whatever means is
>> > > posible, we could modify our goal and plan to release an
>> > > uncertified Java SE runtime, or more radically change Harmony's
goal away from Java SE.
>> >
>> > Previously the situation was that Harmony didn't *want* to pass the
JCK, Harmony *had* to pass the JCK in order to be able to make a
release.
>> Well, not really.  We have always said that Harmony's goal was for a
compatible and compliant implementation of Java SE.  Passing the JCK
has a number of advantages, including the ability to demonstrate to our
users that Harmony is 'real' Java.
>
> Indeed.  Passing the TCK is key to our goal to be "compatible and
compliant".  We *need* to pass the TCK to meet the goal of being
compliant, but we also *want* to pass the TCK as it is a good measure
(arguably the best measure) of our being "compatible".

Passing the TCK was also presented as being the key to "SUN's intellectual
property rights that are essential to practice this specification".  Of
course a company that can refuse access to the TCK can also find an excuse
not to grant those rights anyway.

> Passing the TCK is also important to gaining credibility with some
potential users.
>
>> > But that was all based on agreements and contracts which have now
been unequivocally abrogated, so I guess it doesn't matter much any
more. In which case I think Harmony should turn its back on the JCK
and instead seek to be as compatible as possible "by whatever means
is posible".
>> I've certainly hear others making that argument too -- that is to say,
continue with the goal of of full Java compatible runtime, and accept
that Harmony won't be certified.  Of course, there are other assurances
and rights that come with passing the JCK, and so it would be
interesting to hear the importance that contributors and consumers of
Harmony place on that.

To me as a potential contributor it matters not one hoot.  Consumers may
have other reactions, of which more anon.

> A year ago several people were suggesting that we might take a stand and
release Harmony.  To take one random example:
>
>   http://www.jroller.com/niclas/entry/oracle_s_java_community_commitment
>
> Even ignoring changes since that time, I think this misses the
> important point that no matter how safe we, the ASF, think we are there
is no point making releases that no one (with more to lose?) would risk
using.

Among users (and potential users) of "alternative" runtimes that I have
talked to there is a very broad range of viewpoints.  Some indeed (those
with the most active License Review Boards) do take the line that they
would not want to use anything which carries the tiniest risk of legal
complications. (Of course this risk can never be eliminated entirely,
witness the Wang/Kodak debacle as well as SCO).  Others are surprisingly
sanguine about the whole affair, apparently regarding the current
Oracle/Google kerfuffle as a kind of celebrity scandal diversion rather
than something that might affect them directly.  Yes, on the whole larger
companies tend to be more cautious than small ones in this respect but I
still know some major players who are using "unlicensed" JREs in some
product or other.

> So my problem with taking anything but the "continue with the current
goal and encourage the Apache Board to seek the JCK license by
> whatever means is posible" option is that I believe that the other
options I can imagine are rather short on potential users.
>
> That said, from a purely technical perspective some of the other options
are rather appealing so I'd be happy to be convinced my
> non-technical conclusions are wrong.

Precisely - from a technical point of view one would prefer to think that
this was all just some silly tantrum on the part of Java's new
owners/custodians and once it is all over Java will be freer than ever.
But I have to admit that it may turn out otherwise and then some of us may
have to accept that our efforts have been in vain.  For the time being I
prefer to keep the flame burning.

Best regards

Chris Gray





Re: [general] Harmony future roadmap

Posted by Mark Hindess <ma...@googlemail.com>.
In message <4C...@gmail.com>, Tim Ellison writes:
>
> On 31/Oct/2010 20:23, chris.gray@k-embedded-java.com wrote:
> >
> > Tim Ellison wrote:
> > >
> > > I think all options and opinions are open for discussion.  We
> > > could simply continue with the current goal and encourage the
> > > Apache Board to seek the JCK license by whatever means is
> > > posible, we could modify our goal and plan to release an
> > > uncertified Java SE runtime, or more radically change Harmony's
> > > goal away from Java SE.
> > 
> > Previously the situation was that Harmony didn't *want* to pass the
> > JCK, Harmony *had* to pass the JCK in order to be able to make a
> > release.
>
> Well, not really.  We have always said that Harmony's goal was for a
> compatible and compliant implementation of Java SE.  Passing the JCK
> has a number of advantages, including the ability to demonstrate to
> our users that Harmony is 'real' Java.

Indeed.  Passing the TCK is key to our goal to be "compatible and
compliant".  We *need* to pass the TCK to meet the goal of being
compliant, but we also *want* to pass the TCK as it is a good measure
(arguably the best measure) of our being "compatible".

Passing the TCK is also important to gaining credibility with some
potential users.
 
> > But that was all based on agreements and contracts which have now
> > been unequivocally abrogated, so I guess it doesn't matter much any
> > more. In which case I think Harmony should turn its back on the JCK
> > and instead seek to be as compatible as possible "by whatever means
> > is posible".
>
> I've certainly hear others making that argument too -- that is to
> say, continue with the goal of of full Java compatible runtime, and
> accept that Harmony won't be certified.  Of course, there are other
> assurances and rights that come with passing the JCK, and so it would
> be interesting to hear the importance that contributors and consumers
> of Harmony place on that.

A year ago several people were suggesting that we might take a stand and
release Harmony.  To take one random example:

  http://www.jroller.com/niclas/entry/oracle_s_java_community_commitment

Even ignoring changes since that time, I think this misses the
important point that no matter how safe we, the ASF, think we are
there is no point making releases that no one (with more to lose?)
would risk using.

So my problem with taking anything but the "continue with the current
goal and encourage the Apache Board to seek the JCK license by
whatever means is posible" option is that I believe that the other
options I can imagine are rather short on potential users.

That said, from a purely technical perspective some of the other
options are rather appealing so I'd be happy to be convinced my
non-technical conclusions are wrong.

Regards,
 Mark.





Re: [general] Harmony future roadmap

Posted by Tim Ellison <t....@gmail.com>.
On 31/Oct/2010 20:23, chris.gray@k-embedded-java.com wrote:
>> I think all options and opinions are open for discussion.  We could
>> simply continue with the current goal and encourage the Apache Board to
>> seek the JCK license by whatever means is posible, we could modify our
>> goal and plan to release an uncertified Java SE runtime, or more
>> radically change Harmony's goal away from Java SE.
> 
> Previously the situation was that Harmony didn't *want* to pass the JCK,
> Harmony *had* to pass the JCK in order to be able to make a release.

Well, not really.  We have always said that Harmony's goal was for a
compatible and compliant implementation of Java SE.  Passing the JCK has
a number of advantages, including the ability to demonstrate to our
users that Harmony is 'real' Java.

> But that was all based on agreements and contracts which have now
> been unequivocally abrogated, so I guess it doesn't matter much any
> more. In which case I think Harmony should turn its back on the JCK
> and instead seek to be as compatible as possible "by whatever means
> is posible".

I've certainly hear others making that argument too -- that is to say,
continue with the goal of of full Java compatible runtime, and accept
that Harmony won't be certified.  Of course, there are other assurances
and rights that come with passing the JCK, and so it would be
interesting to hear the importance that contributors and consumers of
Harmony place on that.

> The only question is whether Harmony should try to track
> the whole of Java 7 and 8 or try to stick with a "core" and leave the
> rest to other (possibly Apache) projects.

When you say "a core" I assume you mean Java 5 SE and/or Java 6 SE?

> "Modularising" Java in this way would already be a radical departure from
> the way Sun/Oracle have been handling the development of Java, and Harmony
> clearly has something to contribute here.  I have an inkling that such a
> "modularised" Java would be popular in enterprise computing - but as you
> know my personal interest is in the embedded kind.  In the past Harmony
> (or at least Geir) was reluctant to open up a "second front" on the
> embedded side, but now there seems to be nothing to be gained by such
> restraint ...

That may have been true in the distant past, but I hope you didn't feel
that to be the case recently.

> I'd like to make an analogy with Darwin.  (Yes, I'm a closet FreeBSD guy.)
>  Darwin is basically the FreeBSD userland that Apple distributes as part
> of OS X, without the apple-specific GUI.  (Apple also use a different OS
> kernel.)  So for FreeBSD substitute Harmony, and for Apple substitute
> another commercially successful company (which uses a different VM), and
> what do we have?  I think we have a very interesting modular approach to
> Java for mobile and embedded.

I'm assuming here that you are no longer talking about a Java SE or Java
ME compatibility story, but setting out on a new platform definition for
Harmony?

>> [1] e.g. http://s.apache.org/xI
> 
> BTW this link seems to be broken.

Works for me, it should expand out to

https://blogs.apache.org/foundation/entry/statement_by_the_asf_board

Regards,
Tim


Re: [general] Harmony future roadmap

Posted by ch...@k-embedded-java.com.
Hi Tim,

> I think all options and opinions are open for discussion.  We could
simply continue with the current goal and encourage the Apache Board to
seek the JCK license by whatever means is posible, we could modify our
goal and plan to release an uncertified Java SE runtime, or more
radically change Harmony's goal away from Java SE.

Previously the situation was that Harmony didn't *want* to pass the JCK,
Harmony *had* to pass the JCK in order to be able to make a release. But
that was all based on agreements and contracts which have now been
unequivocally abrogated, so I guess it doesn't matter much any more.  In
which case I think Harmony should turn its back on the JCK and instead
seek to be as compatible as possible "by whatever means is posible".  The
only question is whether Harmony should try to track the whole of Java 7
and 8 or try to stick with a "core" and leave the rest to other (possibly
Apache) projects.

"Modularising" Java in this way would already be a radical departure from
the way Sun/Oracle have been handling the development of Java, and Harmony
clearly has something to contribute here.  I have an inkling that such a
"modularised" Java would be popular in enterprise computing - but as you
know my personal interest is in the embedded kind.  In the past Harmony
(or at least Geir) was reluctant to open up a "second front" on the
embedded side, but now there seems to be nothing to be gained by such
restraint ...

I'd like to make an analogy with Darwin.  (Yes, I'm a closet FreeBSD guy.)
 Darwin is basically the FreeBSD userland that Apple distributes as part
of OS X, without the apple-specific GUI.  (Apple also use a different OS
kernel.)  So for FreeBSD substitute Harmony, and for Apple substitute
another commercially successful company (which uses a different VM), and
what do we have?  I think we have a very interesting modular approach to
Java for mobile and embedded.

> [1] e.g. http://s.apache.org/xI

BTW this link seems to be broken.

Best regards

Chris