Re: [ee4j-pmc] Maven release plans for Batch (JSR 352) APIs with Jakarta

["Scott Kurz" <skurz@xxxxxxxxxx>]

Following up on my plans to release the previous javax.batch artifact as a jakarta.batch artifact....

It dawned on me that batch has (compile) dependencies on other javax.* artifacts:
*javax.inject:javax.inject:1
* javax.enterprise:cdi-api:1.1-20121030 (probably should be 1.1 as in EE 7 POM; haven't heard of any issues though)

I did catch in : https://docs.google.com/document/d/1pm8fjNusxxecoI-9M-eYvnoTkmZTMraQETN7OeVyMnA/edit# that javax.inject will not be moved, but I'm wondering what the plans are for the CDI API?

---

Haven't thought this through completely, but in switching group,artifact ids, we're preventing Maven from doing its normal dependency conflict resolution.

So if I release jakarta.batch at 1.0.1,and CDI 2.x is released under a jakarta.* group id, say, including both could cause issues since both CDI 1.1 and 2.0 end up on the classpath (I'd think?).. or the need for "exclusions".
So we'd just have to release jakarta.batch again, as 1.0.2. (And I guess by this logic, it'd probably makes sense to wait to release any Jakarta aggregates until all the components are moved.)

On the other hand, you could say, so what? You often have to update Maven coordinates. But... is this a special case, the grand entry of a new set of jakarta.* group ids into the world? Where we should get it "right" on the initial release ?

Skimming over the list archives I don't see any discussion here jumping out at me. Wondering what the PMC take on this is.

In any case, seems like the next step is to ask what the plans are for CDI with respect to Maven and jakarta coordinates, and will see what I can find.

Regards,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Compute Grid
Development and Level 3 Team Lead
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102544
skurz@xxxxxxxxxx
--------------------------------------------------------

"Scott Kurz" ---10/22/2018 08:31:12 AM---To align with the Jakarta EE plans for moving Java EE to Jakarta Maven coordinates (https://urldefen

From: "Scott Kurz" <skurz@xxxxxxxxxx>
To: ee4j-pmc@xxxxxxxxxxx
Date: 10/22/2018 08:31 AM
Subject: [ee4j-pmc] Maven release plans for Batch (JSR 352) APIs with Jakarta group id
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx

---

To align with the Jakarta EE plans for moving Java EE to Jakarta Maven coordinates (https://www.eclipse.org/lists/ee4j-pmc/msg00944.html) and the document at: https://docs.google.com/document/d/1pm8fjNusxxecoI-9M-eYvnoTkmZTMraQETN7OeVyMnA/edit#heading=h.ma7xbsxflh33) 
IBM is posting our plans to release the JSR 352 API (Batch 1.0) into Maven using Jakarta group coordinates. 

That is, we will release the contents of 

current artifact: javax.batch:javax.batch-api:1.0.1 
under new coordinates: jakarta.batch:jakarta.batch-api:1.0.1

Assuming there are no objections, I will contact Sonatype OSSRH and open a ticket, referencing this email, claiming the right to publish to these coordinates, and expect this can all be completed by Oct. 29. 

(I'm also posting this to the batch-spec@xxxxxxxxxxxxxxxx for any comments or questions.)
---

Since the batch specification efforts have been quiet, both with respect to Jakarta and otherwise, let me just pre-emptively answer a few questions:

1. What are IBMs plans for Batch in Jakarta? 

IBM still intends to resume work on a batch specification in Jakarta. The first step will be to establish a corresponding Specification Project for Java Batch. Then, we will entertain the creation of a corresponding implementation project. Exact dates for these exercises have not been determined.

2. Where do I discuss Jakarta Batch?

The batch-spec@xxxxxxxxxxxxxxxx forum is as good as any place for now to designate as an "official" discussion forum, though we recognize that's just a formal designation since discussion is quiet. Also, the jakarta.ee-community@xxxxxxxxxxx email list would seem to be an appropriate place within EE4J to discuss.

3. What about the other Batch artifacts in Maven? 

Only the API is being released under the jakarta maven coordinates at this time.

If you search for other javax.batch artifacts you will find some other uninteresting artifacts: beta-level artifacts we never ended up releasing in 1.0, as well as a "parent POM" module (javax.batch:jbatch:1.0) that we later realized should be moved to a different groupid.

4. Where will the Jakarta release be performed from?

https://github.com/WASdev/standards.jsr352.jbatch

Thank you,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Compute Grid
Development and Level 3 Team Lead
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102544
skurz@xxxxxxxxxx
--------------------------------------------------------_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc