Re: [jakarta.ee-community] Webinar: Creating CI/CD pipelines for EE4J pr

["Kevin Sutter" <sutter@xxxxxxxxxx>]

The content of this note is totally off-topic
from the subject... I almost missed this...

I know we discussed and approved this
usage of "jakarta" over "javax", but what was the expected
timing of this change?  Immediately?  Or, wait until after Eclipse
Glassfish is Java EE 8 compliant, which would then signal the formal start
of Jakarta EE releases.  Specific case...  The recent JAX-RS
2.1.1 update.  If that would have been released this week, should
it have used "jakarta" in it's group and artifact ids?  Or,
should we wait until after we declare that Java EE has successfully transitioned
to Eclipse?

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Java 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 EE community
discussions <jakarta.ee-community@xxxxxxxxxxx>
Date:      
 09/12/2018 05:00 AM
Subject:    
   Re: [jakarta.ee-community]
Webinar: Creating CI/CD pipelines for EE4J projects
Sent by:    
   jakarta.ee-community-bounces@xxxxxxxxxxx

---

Double check your access.  Many people are viewing
it and and I've verified I can see it in a Chrome incognito window not
logged in.

At this time only a simple find/replace of "javax"->"jakarta"
on groupId and artifactId.  No other changes should be made such as
inserting "jakarta" where there was no "javax".


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

On Sep 12, 2018, at 2:35 AM, Werner Keil <werner.keil@xxxxxxxxx>
wrote:

David,

Yep, I recall there already was some form of vote during
the call ;-)
Strange, Otavio did not mention it in his slides at the
JCP EC call, but I guess based on the minutes and your reminder JNoSQL
is also good to use it at least in upcoming presentations like the one
at JCON next month (a bit before ECE and OC1, guess we get a kind of premiere
there)

Does it mean, while the package namespace of jms-api at
least for existing code will stay javax.jms, the groupId in
https://github.com/eclipse-ee4j/jms-api/blob/master/pom.xml(master) should contain "jakarta" already?

That raises a couple of additional questions,
Would

<groupId>javax.jms</groupId>
simply become <groupId>jakarta.jms</groupId> ? Or are there any additional trademark issues that would force us to use "jakarta.ms" instead because the name "Java" must not be used any more?

And obviously artifactIds also have to be changed.

I cannot see the Google Docs but I am pretty sure, we
did not go deep enough into the question of artifactIds yet in the Specification
WG calls I attended, so would the Oracle-enforced artifactId
<artifactId>javax.jms-api</artifactId> 
become
<artifactId>jakarta.jms-api</artifactId> 
or simply
<artifactId>jms-api</artifactId>
 ???

This is not consistently done, e.g. CDI (not a Jakarta
EE spec) never added the "javax" while most of the Java EE 8
specs by Oracle did.

Thanks,
Werner

Werner Keil | JCP Award Winner, JSR 385 Spec
Lead | Eclipse UOMo Lead, Jakarta EE Specification Committee Member | Apache
Committer | JCON 2018 Speaker, AdBoard Member
Twitter @wernerkeil | @UnitAPI | @JSR354
| @AgoravaProj | @TamayaConf | @OpenDDR | #EclipseUOMo
Skype werner.keil




On Wed, Sep 12, 2018 at 11:09 AM David Blevins <dblevins@xxxxxxxxxxxxx>
wrote:
Note, we should release all api jars (not implementations)
to Maven Central under the jakarta groupId.  This is new as of the
August 29th Specification Committee meeting minutes and we'll need to do
some work with Sonatype to get the publishing rights, but heads up.  The
minutes didn't have a link to the doc, so posting a clean version without
the comments here for everyone to see:

 - https://docs.google.com/document/d/1pm8fjNusxxecoI-9M-eYvnoTkmZTMraQETN7OeVyMnA/edit#heading=h.ma7xbsxflh33


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

On Sep 11, 2018, at 1:39 PM, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
wrote:

Hi,

As part of our next weekly build team sync up meeting we are hosting a
webinar “Creating CI/CD pipelines for EE4J projects”. Authors of two
working pipelines Tomas Kraus (JSON-P project) and Markus Karg (JAX-RS
project) will demonstrate their work and explain it in details. Eclipse
webmasters are also participating, so you will have an opportunity to get
answers to your questions about the Eclipse infrastructure. Feel free to
forward this invitation to all interesting parties.

Meeting details:

Creating CI/CD pipelines for EE4J projects
Scheduled: 12 Sep 2018 at 16:00 to 17:00 (CET+1)
Organizers: Dmitry Kornilov, Ed Bratt
----------------------

Zoom: https://zoom.us/my/edbratt

+1 646 558 8656 or +1 669 900 6833 US Toll
Meeting ID: 327 448 7218 
International numbers available: https://zoom.us/u/vtOXR

Thanks,
Dmitry

<iCal-20180907-162357.ics>


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

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