[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Oracle Java EE8 Issue Tracker Abandonment

Dmitry,

Please dont try to twist this into an issue of me publicly posting my opinion in order to prioritize the minor issues that I have submitted. I never once demanded that an issue be solved or prioritized due to its importance. I do think other developers have the right to know that their questions will NOT be answered because there is nobody there to answer them. The worst part of the whole situation was the lack of communication. Had this been communicated, I would have been perfectly content with the fact that no one was actively supporting Jersey due to ongoing EE4J migration issues going on. While developers are submitting issues and patiently asking "Any updates?" after months go by, you guys are aware of these issues, yet are sitting back in silence. I have witnessed this first hand Dmitry, when you miraculously seem to show up at any suggestion of Oracle might not being supporting Java EE8 like the open source champion it claims to be.

-Eric


On Sunday, December 3, 2017, 5:02:19 PM EST, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:


The information posted is wrong. Projects are not dead. And we are not talking about specs here. Both projects are RIs.

This is Yasson dashboard: https://goo.gl/GkG4Gz. Does it look like a dead project graph? Also, version 1.0.1 was released on Nov 10th.

Here is Jersey activity: https://github.com/jersey/jersey/graphs/commit-activity. There are less commits since a stable version was released, but itâs no doubt that work is going on.  

Eric, posting about Java EE 8 death in every single thread wonât change priorities of issues you submitted. The main priority for us is preparing projects for EE4J migration. All other issues (including yours) are in the queue and will be addressed later, when resources are available. It can be even after Jersey->EE4J migration. Be patient.

â
Dmitry

On 3 Dec 2017, at 16:04, Werner Keil <werner.keil@xxxxxxxxx> wrote:

Eric,

I am not sure, which Java EE 8 specs you refer to?

Only 3 examples of Java EE 8 JSRs that also got updates of the codewithin the last 2-7 days:
or

JSR 374 got 2 service releases (1.1.1 and 1.1.2) already since Java EE 8 was published.
Grizzly just made a new release 2 days ago: https://github.com/javaee/grizzly/releases/tag/2_3_34
JTA has an ongoing MR https://jcp.org/aboutJava/communityprocess/maintenance/jsr907/index6.html the EC will have to vote on first thing next year.

While EE4J does not even have a concrete repository until the relevant bodies at Eclipse Foundation (EE4J PMC, Architecture Council, Eclipse Board, IP Lawyers, etc., there are more places things have to be approved by;-) have even approved their creation, the Java EE 8 JSRs remain active. At least until 2025 Oracle stated, it'll support it and we have not even seen any vendor apply Java EE 8 to its products yet, so there may be one or the other improvement and MR before development may stop. As both EE4J and the Java EE JSRs use GitHub, we should not see anything lost, but right now there is no evidence, issues are not worked on at Java EE on GitHub or code is pushed. GitHub is very transparent and makes contributions a lot more visible than java.net or OpenJDK did, so both Java EE 8 and EE4J offer far better transparency.

Werner 


On Sun, Dec 3, 2017 at 9:03 AM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to
        ee4j-community@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        https://dev.eclipse.org/ mailman/listinfo/ee4j- community
or, via email, send a message with subject or body 'help' to
        ee4j-community-request@ eclipse.org

You can reach the person managing the list at
        ee4j-community-owner@eclipse. org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."


Today's Topics:

   1. Oracle Java EE8 Issue Tracker Abandonment (Eric Taylor)
   2. Re: Oracle Java EE8 Issue Tracker Abandonment (Reza Rahman)
   3. Re: Oracle Java EE8 Issue Tracker Abandonment (Markus KARG)
   4. Re: Oracle Java EE8 Issue Tracker Abandonment (Markus KARG)


------------------------------ ------------------------------ ----------

Message: 1
Date: Sat, 2 Dec 2017 18:20:41 +0000 (UTC)
From: Eric Taylor <etay5995@xxxxxxxxx>
To: "ee4j-community@xxxxxxxxxxx" <ee4j-community@xxxxxxxxxxx>
Subject: [ee4j-community] Oracle Java EE8 Issue Tracker Abandonment
Message-ID: <672398188.349609. 1512238841027@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Does anyone want to address the issue of the abandonment of the Issue Trackers for major EE8 specifications? Specifically the Jersey and Yasson issue trackers seem to be dead or dying. I briefly corresponded with Dmitry Kornilov regarding the state of the Jersey issue tracker, and essentially he told me that most of the original employee developers are no longer contributing or even working at Oracle any more. He told me he was working on finding new developers, but this was over a month ago and frankly I have begun to think that Java EE8 is heading down the neglected path that EE7 was on. Issues are piling up and there is no communication between developers to even help facilitate patching and submitting pull requests. Does Oracle have any responsibility left in this, or have they just dumped Java EE8 in the Eclipse Foundation's hands and said "Good luck!"?

Is there a central point of contact regarding EE8 or is communication fragmented across each specification? Should I abandon server side Java and just start using server side _javascript_ (node.js)? Just kidding on the last part. ;)
Thanks,Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/ mailman/private/ee4j- community/attachments/ 20171202/bb12318c/attachment. html>

------------------------------

Message: 2
Date: Sat, 2 Dec 2017 13:35:48 -0500
From: Reza Rahman <reza_rahman@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker
        Abandonment
Message-ID: <3E3E8F5D-6902-408B-A984- AFD84854CAE3@xxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

This is a very real concern for many customers. We heard the same concern at JavaOne during EE4J discussions. As I have said for a while now, the best way to address this is a realistic roadmap for EE4J including some kind of commitment, hopefully including from Oracle, as to who is taking ownership of moving which Java EE specification forward. Simply continuing to say it will take time to figure out risks people continuing to worry more and more about the future of Java EE.

At least a simple list of who wants to move which specification forward should not be so hard for a technology and market as mature as Java EE.

Sent from my iPhone

> On Dec 2, 2017, at 1:20 PM, Eric Taylor <etay5995@xxxxxxxxx> wrote:
>
> Does anyone want to address the issue of the abandonment of the Issue Trackers for major EE8 specifications? Specifically the Jersey and Yasson issue trackers seem to be dead or dying. I briefly corresponded with Dmitry Kornilov regarding the state of the Jersey issue tracker, and essentially he told me that most of the original employee developers are no longer contributing or even working at Oracle any more. He told me he was working on finding new developers, but this was over a month ago and frankly I have begun to think that Java EE8 is heading down the neglected path that EE7 was on. Issues are piling up and there is no communication between developers to even help facilitate patching and submitting pull requests. Does Oracle have any responsibility left in this, or have they just dumped Java EE8 in the Eclipse Foundation's hands and said "Good luck!"?
>
> Is there a central point of contact regarding EE8 or is communication fragmented across each specification? Should I abandon server side Java and just start using server side _javascript_ (node.js)? Just kidding on the last part. ;)
>
> Thanks,
> Eric
> ______________________________ _________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/ mailman/listinfo/ee4j- community
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/ mailman/private/ee4j- community/attachments/ 20171202/bac0b037/attachment. html>

------------------------------

Message: 3
Date: Sun, 3 Dec 2017 08:56:27 +0100
From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
To: "'EE4J community discussions'" <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker
        Abandonment
Message-ID: <003001d36c0c$3bf51080$ b3df3180$@eu>
Content-Type: text/plain; charset="utf-8"

Eric,



please do not abandon server-side Java. ;-)



The transition of Jersey (and a lot more projects) from Oracle to the Eclipse Foundation is in progress. As you could imagine, this involves a lot of organizational issues. So this will take a while. Stay tuned, everything will be fine in the end. :-)



-Markus





From: ee4j-community-bounces@ eclipse.org [mailto:ee4j-community- bounces@xxxxxxxxxxx] On Behalf Of Eric Taylor
Sent: Samstag, 2. Dezember 2017 19:21
To: ee4j-community@xxxxxxxxxxx
Subject: [ee4j-community] Oracle Java EE8 Issue Tracker Abandonment



Does anyone want to address the issue of the abandonment of the Issue Trackers for major EE8 specifications? Specifically the Jersey and Yasson issue trackers seem to be dead or dying. I briefly corresponded with Dmitry Kornilov regarding the state of the Jersey issue tracker, and essentially he told me that most of the original employee developers are no longer contributing or even working at Oracle any more. He told me he was working on finding new developers, but this was over a month ago and frankly I have begun to think that Java EE8 is heading down the neglected path that EE7 was on. Issues are piling up and there is no communication between developers to even help facilitate patching and submitting pull requests. Does Oracle have any responsibility left in this, or have they just dumped Java EE8 in the Eclipse Foundation's hands and said "Good luck!"?



Is there a central point of contact regarding EE8 or is communication fragmented across each specification? Should I abandon server side Java and just start using server side _javascript_ (node.js)? Just kidding on the last part. ;)



Thanks,

Eric

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/ mailman/private/ee4j- community/attachments/ 20171203/db46360e/attachment. html>

------------------------------

Message: 4
Date: Sun, 3 Dec 2017 09:03:51 +0100
From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
To: "'EE4J community discussions'" <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker
        Abandonment
Message-ID: <005401d36c0d$44a33e40$ cde9bac0$@eu>
Content-Type: text/plain; charset="utf-8"

Reza,



be assured, behind the scenes people do work on the migration. At least I do know that for some of the projects, in particular Jersey. A first bunch of projects is currently in progress, other bunches will follow. But yes, certainly it would be really great to have a weekly updated web site showing the content that is currently moved and the particular progress (like "Jersey: xx%") so this is publicly trackable. I CC'ed PMC head Ivar Grimstad about this, maybe he can trigger the Eclipse Foundation to set up such a web site?



-Markus





From: ee4j-community-bounces@ eclipse.org [mailto:ee4j-community- bounces@xxxxxxxxxxx] On Behalf Of Reza Rahman
Sent: Samstag, 2. Dezember 2017 19:36
To: EE4J community discussions
Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker Abandonment



This is a very real concern for many customers. We heard the same concern at JavaOne during EE4J discussions. As I have said for a while now, the best way to address this is a realistic roadmap for EE4J including some kind of commitment, hopefully including from Oracle, as to who is taking ownership of moving which Java EE specification forward. Simply continuing to say it will take time to figure out risks people continuing to worry more and more about the future of Java EE.



At least a simple list of who wants to move which specification forward should not be so hard for a technology and market as mature as Java EE.

Sent from my iPhone


On Dec 2, 2017, at 1:20 PM, Eric Taylor <etay5995@xxxxxxxxx> wrote:

Does anyone want to address the issue of the abandonment of the Issue Trackers for major EE8 specifications? Specifically the Jersey and Yasson issue trackers seem to be dead or dying. I briefly corresponded with Dmitry Kornilov regarding the state of the Jersey issue tracker, and essentially he told me that most of the original employee developers are no longer contributing or even working at Oracle any more. He told me he was working on finding new developers, but this was over a month ago and frankly I have begun to think that Java EE8 is heading down the neglected path that EE7 was on. Issues are piling up and there is no communication between developers to even help facilitate patching and submitting pull requests. Does Oracle have any responsibility left in this, or have they just dumped Java EE8 in the Eclipse Foundation's hands and said "Good luck!"?



Is there a central point of contact regarding EE8 or is communication fragmented across each specification? Should I abandon server side Java and just start using server side _javascript_ (node.js)? Just kidding on the last part. ;)



Thanks,

Eric

______________________________ _________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/ mailman/listinfo/ee4j- community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/ mailman/private/ee4j- community/attachments/ 20171203/53bd4b3c/attachment. html>

------------------------------

______________________________ _________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/ mailman/listinfo/ee4j- community


End of ee4j-community Digest, Vol 4, Issue 29
****************************** ***************

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

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