Use Advanced Search to search the entire archive.
[jsr363-experts] Eclipse Orbit
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Eclipse Orbit
- Date: Thu, 20 Aug 2015 13:56:34 +0200
Dear Experts,
I recently had to close
https://java.net/jira/browse/UNITSOFMEASUREMENT-64
because the Eclipse IP legal team signalled in the related IPZilla tickets,
they were unwilling or unable to accept the public API of JSR 363 into
Orbit to be used by Eclipse projects like SmartHome, uDig, etc.
A follow-up discussion involving JCP Chair Patrick Curran (the PMO) as well
as Eclipse staff including Mike Milinkovich is still pending a clear answer
if it could be accepted should we e.g. place the BSD license text file in
the repository of Unit-API instead of the Spec License (which seems to be a
problem for Eclipse)
Many Eclipse projects especially those under an umbrella like OpenJDK, Java
EE, etc. seem to do that, take JSR 375 where I'm in the EG as one example.
A few, primarily JSR 107 did this "by the book" from a JCP point. Those who
were in the JSR 275 EG already will remember, Jean-Marie and I were
explicitely asked to to the exact opposite, replace the BSD license with
the Spec License prior to Public Review (neither was a key reason why it
went negative later;-)
JSR 107 was started even before 108, our first "ancestor" JSR but that
produced too little to tell, if a LICENSE.txt file was even in place or
discussed.
A few "standalone" JSRs that are not under an umbrella, especially JSR 354
also use the Spec License. More importantly they have the whole spec in
Asciidoc in the same repository.
So does JSR 375, being Oracle lead (sure 107 also has a Co-Spec Lead), too.
We have to wait if the question gets answered in a satisfactory manner. No
reason to try another CQ before that. However, since it became evident,
some projects especially uDig use far older JSR 275 versions (due to a
mistake when that was entered into Orbit instead of the later version
actually used by GeoAPI 3.0, too) I hope it's in everybody's interest, also
Eclipse, to make this JSR available in Orbit soon.
Public Draft (0.8) isn't too far, so instead of an EDR revival, it sounds
better to wait till 0.8 is complete enough to be proposed for Public
Review. And either in parallel or no later than after the review ballot,
hopefully Orbit may also give home to that API version.
Kind Regards,
Werner