Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Java EE Guardians Statement on Oracle/Eclipse Agreement

Thanks for confirmation, Bill! That’s what I thought. 

On Jun 6, 2019, at 2:25 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

The javax APIs in Java SE follow the JCP rules.  The issue arises for the Java EE APIs because we're no longer going to use the JCP.

Manik Magar wrote on 6/6/19 9:08 AM:
So do these javax namespace usage rules apply to APIs contained in Java SE too? If it doesn't then it is less of a concern, IMO. They will just stay javax always. As Mike mentioned in his article, even a maintenance change would result in changing namespace in an API specification. That is what concerning if all are not changed now but touched in later releases for maintenance.


Regards,
Manik Magar




On Thu, Jun 6, 2019 at 1:35 AM Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
Manik,

FYI no matter what EE does, there are going to be javax APIs that remain as they are provided by the JRE and not the container.  Thus a mix is going to occur no matter what.  Below is a list of what I can see in a JDK11 release and sql, xml, transaction, naming are all very relevant to EE applications.

cheers


javax/security
javax/annotation
javax/lang
javax/tools
javax/swing
javax/sound
javax/print
javax/swing
javax/imageio
javax/accessibility
javax/management
javax/naming
javax/rmi
javax/script
javax/security
javax/smartcardio
javax/sql
javax/transaction
javax/xml

On Thu, 6 Jun 2019 at 03:40, Manik Magar <manik.magar@xxxxxxxxx> wrote:
Hi,

Even though javax.* package naming can be used as-is, having a mix of javax.* and jakarta.* could complicate migrations. I would rather prefer to have application migration done once than little bit every time. IMO, javax.* to jakarta.* migration should be part of Jakarta EE 9, even if that means that is the only change for it. That could give a clean start for future releases. So, Big bang approach. With that said, I think MicroProfile can stay independent for Jakarta EE 9 release.  


Regards,
Manik Magar

On Jun 3, 2019, at 5:13 PM, Ryan Cuprak <rcuprak@xxxxxxxxx> wrote:

Hello,
 A heads-up to those on this list, the Java EE Guardians have published a statement on the agreement between Oracle and Eclipse: 

Regards,
-Ryan

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev


--
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev


Back to the top