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

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@xxxxxxxxxxx [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