Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] Automation for creating boilerplate-spec PRs
I don't recall seeing the guidance that EE4J_8 was no longer required and I was assuming that all this work for the Jakarta EE 8 release (specifications and so on) would still be on EE4J_8.

On Thu, 11 Jul 2019 at 19:53, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
I'm doing two PRs and leaving it up to the projects which one(s) they want to merge.

Our previous guidance was projects had to keep the EE4J_8 branch for the eventual Jakarta EE 8 release and could play outside that branch.  At that time some projects started using master for their Jakarta EE.next work and master has long since diverged.   Some have even done javax to jakarta namespace migrations:

 - https://github.com/eclipse-ee4j/jaxrs-api/tree/master/jaxrs-api/src/main/java/jakarta/ws/rs

Dmitry did both branches for his jsonb-api work as well:


So I figured better safe than sorry :)

On Jul 11, 2019, at 11:08 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

The EE4J_8 branch is dead.  They should all have been merged into master by now.

Kevin Sutter wrote on 7/11/19 7:46 AM:
Thanks, David.

On a side note...  I noticed that your PR is for the EE4J_8 branch.  I know that we set up that requirement for the first release, but was that just for the jakarta maven coordinates release?  Or, should we all still be using the EE4J_8 branch for this first Jakarta EE 8 release?  I see it on our wiki, but looking for interpretation from anyone...

For example, we've been doing the Platform Spec updates directly into Master.  Since we're not performing any other changes beyond Jakarta EE 8 at this time, I think that's okay.  But, I suppose using an alternate branch might be very helpful for projects that are already looking beyond Jakarta EE 8...

Requirement?  Strong suggestion?  Other?

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        David Blevins <dblevins@xxxxxxxxxxxxx>
To:        Jakarta specification disccusions <jakarta.ee-spec@xxxxxxxxxxx>
Date:        07/11/2019 09:28 AM
Subject:        [EXTERNAL] [jakarta.ee-spec] Automation for creating boilerplate-spec PRs
Sent by:        jakarta.ee-spec-bounces@xxxxxxxxxxx



End-to-end success achieved on jms-api:

 - https://github.com/eclipse-ee4j/jms-api/pull/225

Generator source is here:

 - https://github.com/jakartaee/specification-tools

Tried ejb-api and management-api.  Notice some differences that threw the generator off.  Didn't look serious.  Pulled an all-nighter so going to get a few hours of sleep then try on some other projects.

--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec




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

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

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

Back to the top