[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Retaining History for incoming EE4J Projects
|
On Sunday, January 14, 2018, Werner Keil <
werner.keil@xxxxxxxxx> wrote:
Mike,
Thanks for the clarification. Although Oracle representatives or Spec Leads confirmed they do not seek major updates to Java EE standards now placed under the EE4J umbrella, there could be some major issues or bugs the original codebase (through the Maintenance Lead or in some cases former EG Members who signed the OCA) must address to fix them in products and solutions based on Java EE 8.
I do wonder a bit how that would work. Both EE 7 and EE 8 are “current” products. If I’d like to fix a bug in JSF 2.2 from EE 7, how would that be done generally speaking?
As the current Mojarra 2.2 branch (state) wouldn’t exist in the transferred code, would a request to Oracle be done then to publish a new version?
Related to this, are the existing Maven coordinates for various products (like Mojarra) transferred, or would Eclipse Mojarra have to be published using new coordinates?
Kind regards,
Arjan
So it is more or less a fork even if critical bugs may be fixed in both, but it would rarely be via an actual PR from one repository to the other. That is the only way one might see them connected.
Regards,