That is not a package name, that is a module name. Java is Oracle's brand. Oracle did not donate any brand. Any use of their brands has to be negotiated explicitly between Oracle and the Eclipe Foundation. Oracle, and only Oracle, may allow or disallow further use. -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Derek Moore Sent: Freitag, 30. März 2018 16:04 To: jaxrs developer discussions Subject: Re: [jaxrs-dev] Automatic-Module-Name (was: Java version) I don’t understand how that could be up to Oracle. If they are donating EE 8, then these package names are covered by the liberal license of that donation. If Eclipse tries to rename packages, then development will fork and leave the Eclipse Foundation. Asuming it was already there on 2.1 release, I consider it part of the API so I hope it can be kept. Automatic-Module-Name: java.ws.rs is already created by pom.xml of master branch. I assume we can keep that, but it is up to Oracle to decide if we must get rid of the java prefix. -Markus +1 for an automatic module name. Santiago, do you know if we'll be able to use the "java" namespace for the module name as this is an existing spec? Well there actually is one thing in Java 9 that does not exist in Java 8: Modules. The JAX-RS EG dropped modules support back in JAX-RS 2.1 as we had to release BEFORE Java 9 was there. Having a module-info is beneficial to clarify how JAX-RS API behaves when running on Java 9. OTOH we could simply provide Automatic-Module-Name instead. -Markus But is there anything in Java 9 that we actually need? We should probably build on Java 9 or 10 to verify that there are no problems with those, but dropping backwards compatibility without any need for it? I guess it would be best to build JAX-RS 2.2 on Java 8 and 10. 2018-03-29 20:21 GMT+02:00 Christian Kaltepoth <christian@xxxxxxxxxxxx>: I'm fine with adjusting the minimum Java version to 9 for JAX-RS 2.2. But I think it is too early to talk about requirements for JAX-RS 3.0. AFAIK, *Oracle JDK 11* will be LTS, but at that point, only OpenJDK will remain free (which won't hace LTS). So it's not Java 11 that will be LTS, but some specific implementations. Btw, IBM already announced they plan to offer free LTS support for Eclipse OpenJ9 11. Please correct me if I'm wrong. 2018-03-29 19:55 GMT+02:00 Markus KARG <markus@xxxxxxxxxxxxxxx>: I think it would be a good thing to use Java 10 for 3.0 and Java 8 for 2.2. The reason is that people would think they can drop-in 2.2 where currently 2.1 runs -- which is Java EE 8 containers. -Markus Hi all, I'm currently preparing the Travis CI configuration. As part of that, we have to decide against which java versions we want to run the build. Please note that we can run multiple builds against different versions in parallel. I just had a look at the pom and I'm a bit confused about this part. If I read it correctly, the source code version is basically set to the version of the executing JDK. Does this make sense? It seems a bit weird. Isn't the source (and target) version usually the minimum Java version supported? _______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
-- _______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________ jaxrs-dev mailing list jaxrs-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
|