MicroProfile Fault Tolerance 2.0-RC1 was released

56 views
Skip to first unread message

Emily Jiang

unread,
Jan 14, 2019, 6:45:29 AM1/14/19
to Eclipse MicroProfile
I am pleased to say that we have released MicroProfile Fault Tolerance 2.0-RC1. The full details can be found here. Please shout if you have any comments.

Thanks
Emily

Kevin Sutter

unread,
Jan 15, 2019, 9:28:00 AM1/15/19
to Eclipse MicroProfile
Emily,
Somewhere we need to highlight the fact that the only reason you increased the major version number to "2" was because you are dropping the support for Java EE 7.  Since the MicroProfile 2.x releases are all based on Java EE 8 already, dropping support for Java EE 7 is not considered a "breaking change" and will still be allowed in the MicroProfile 2.2 release.  We really need to be up-front about this and document this somewhere.  I didn't find anything on your github Release page, nor did I find anything in the first several pages of the spec.

Thanks,
Kevin

Emily Jiang

unread,
Jan 15, 2019, 9:49:01 AM1/15/19
to Eclipse MicroProfile
Good point. How about highlighting the version change in the spec's release note section? I will put a note on the release page.

Emily

Kevin Sutter

unread,
Jan 15, 2019, 3:00:59 PM1/15/19
to Eclipse MicroProfile
Sure, both places would be good, Emily.  Thanks!

Is Fault Tolerance 2.0 deliberately not supporting Java EE 7?  That is, is FT 2.0 changing some aspect of their implementation where they can no longer support Java EE 7?  Some aspect of Java EE 8 (ie. JSON-B, etc) is now a requirement?  Just curious.  If FT 2.0 could still work with Java EE 7, then I would suggest just bumping your minor version.  That way, users could still use FT 1.x with a Java EE 7 app server.

-- Kevin

Emily Jiang

unread,
Jan 15, 2019, 6:31:33 PM1/15/19
to Eclipse MicroProfile
Kevin,
The Fault Tolerance 2.0 is deliberately not supporting Java EE7 as it needs CDI 2.0 (using some new CDI 2.0 functionality). FT 1.0 and FT 1.1 can work with CDI 1.2 or CDI 2.0. FT 2.0 can only work with CDI 2.0 or 2.0+.

I have added some clarification in the spec on the version change. More details can be found here .

Thanks
Emily

Kevin Sutter

unread,
Jan 16, 2019, 10:15:14 AM1/16/19
to Eclipse MicroProfile
Thanks for the clarification!

John Clingan

unread,
Jan 22, 2019, 8:35:06 PM1/22/19
to Eclipse MicroProfile
Email, I noticed that you have not created a CQ (assuming I searched the CQ list properly :-) ).

I found 3 items that would need to be included in a CQ:

1) Updated GAV (upgraded from 1.x): javax.enterprise:cdi-api:2.0
2) New GAV:  org.jboss.shrinkwrap:shrinkwrap-api:1.2.6
3) New GAV:  org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-impl-javaee:2.0.0

Have you submitted this or do you plan to?

Emily Jiang

unread,
Jan 23, 2019, 9:00:47 AM1/23/19
to Eclipse MicroProfile
Thank you for the thorough check!
The cdi-api:2.0 is included in MP 2.0. The CQ would have been done. However, when I double checked spreadsheet, I cannot find the entry. The spreadsheet seems stale as it did not have any new entries for MP 2.0. Kevin, do you know whether anyone has done CQ for Java EE8 inclusion for JAX-RS, CDI, JSON-P and JSON-B?

As for the shrinkwrap ones as per your email, they have been approved previously by Kevin via CQ15198 and documented in the 3rd spreadsheet.


Thanks
Emily

Kevin Sutter

unread,
Jan 23, 2019, 9:50:12 AM1/23/19
to MicroProfile
Emily,
John actually did the 2.0 release.  I did the 1.4 release.  But, in either case, it doesn't look like we did the CQ updates for the Java EE 8 artifacts...  Darn!  I'll submit them now...  But, to be honest, these could have been submitted by the individual Components...  Remembering to do these Dependency updates is a pain...

Thanks, Emily and John for finding these!
-- Kevin

--
You received this message because you are subscribed to a topic in the Google Groups "Eclipse MicroProfile" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/microprofile/73ms4W_2EY4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/8c4f5192-a8a0-460e-abc4-020871576203%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Emily Jiang

unread,
Jan 23, 2019, 11:02:58 AM1/23/19
to Eclipse MicroProfile
Thank you Kevin for sorting it out! I should have double checked the spreadsheet instead of assuming it has been done.

+1 on remembering to do the checks! I have now added this check to the most popular release wiki so that people won't forget this checklist. I know the checklist is on the top level release wiki, but I think most people follow the instruction from Jenkins link forward:o. Hope this will reduce the chance of missing CQs in our future releases!

Thanks
Emily

Kevin Sutter

unread,
Jan 24, 2019, 12:21:10 PM1/24/19
to Eclipse MicroProfile
Emily,
I don't think the link you provided on the Release wiki is working...  It's taking me to a non-existent page...  Can you straighten that out?  Thanks.

Also, John and I figured out that I actually did the 2.0 release.  John did the 1.4 release...  So, my mistake!   Anyway, we are both working to get this cleaned up.  Of the five updated Java EE components introduced in 2.0, three were already approved by other projects (these are called piggyback CQs).  The other two (jsonb 1.0 and jsonp 1.1) are being worked as we speak.  Hopefully, this doesn't affect our release schedule...

Thanks,
Kevin

Emily Jiang

unread,
Jan 24, 2019, 5:41:42 PM1/24/19
to Eclipse MicroProfile
Thanks Kevin for pointed it out! I figured it out this morning but did not manged to fix it then. It is now fixed.

Emily
Reply all
Reply to author
Forward
0 new messages