Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Maven release plans for Batch (JSR 352) APIs with Jakarta group id

Let me announce I just did a staging release of jakarta.batch:jakarta.batch-api:1.0.1 to the Sonatype OSSRH staging repository.

Since Batch is not currently developed as part of an EE4J project, it seems the release review process isn't a good fit.

Instead I thought I'd just leave it in the staging repository for a time, share some notes in this email, and see if there are any comments before releasing.
---

1. The staging artifacts are at: https://oss.sonatype.org/content/groups/staging/jakarta/batch/jakarta.batch-api/1.0.1/

2. Noting some mentions of JAR Manifest entries recently, I updated these manifest entries: (javax =>jakarta).

Bundle-Name: jakarta.batch-api
Bundle-SymbolicName: jakarta.batch-api
Extension-Name: jakarta.batch

I think the original entries were made following advice from Oracle on following patterns, for OSGi, etc. (I have to admit to being unfamiliar with "Extension-Name").

The full change itself can be seen by: https://github.com/WASdev/standards.jsr352.jbatch/pull/59/files

3. How to test staged artifacts

a) Running the Batch 1.0 TCK against the API, using Jakarta coordinates (assumes jakarta.batch:jakarta.batch-api:1.0.1 in local repo)
https://github.com/WASdev/standards.jsr352.tck/tree/1.0-against-jakarta

b) Another test (gets jakarta.batch:jakarta.batch-api:1.0.1 from staging repo)
https://github.com/scottkurz/sample.batch.bonuspayout/pull/5

4. Finally, I did NOT worry about JPMS module name for this first release

Please let me know of any comments or concerns.

Thanks,
------------------------------------------------------
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
--------------------------------------------------------

Inactive hide details for "Scott Kurz" ---10/31/2018 03:18:06 PM---That's not my role, and I don't have anything to note about "Scott Kurz" ---10/31/2018 03:18:06 PM---That's not my role, and I don't have anything to note about IBM + Red Hat in particular.

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




That's not my role, and I don't have anything to note about IBM + Red Hat in particular.

But let me just say that I did contact Red Hat and got a response that someone will be following-up on my question (didn't say when).

In the meantime I'll keep an eye on the module name issue discussion that Ray pointed us to (thank you), so we can be prepared on that front as well.

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
--------------------------------------------------------

Inactive hide details for arjan tijms ---10/28/2018 04:57:28 PM---Hi, It's probably a bit too early to say anything about it, barjan tijms ---10/28/2018 04:57:28 PM---Hi, It's probably a bit too early to say anything about it, but with IBM having

From: arjan tijms <arjan.tijms@xxxxxxxxx>
To: ee4j-pmc PMC List <ee4j-pmc@xxxxxxxxxxx>
Date: 10/28/2018 04:57 PM
Subject: Re: [ee4j-pmc] Maven release plans for Batch (JSR 352) APIs with Jakarta group id
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx



Hi,

It's probably a bit too early to say anything about it, but with IBM having bought Red Hat, will this change anything regarding CDI moving to Jakarta?

Kind regards,
Arjan

On Sun, Oct 28, 2018 at 8:52 PM Raymond Auge <raymond.auge@xxxxxxxxxxx> wrote:
      It might be worth considering what the module name should be so that downstream projects can begin to think about it. I don't see a module name set in the pom. Note the module name issue being discussed here https://github.com/eclipse-ee4j/ee4j/issues/34

      Sincerely,
      - Ray

      On Thu, Oct 25, 2018 at 3:18 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
      >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.

      I'm really wondering about CDI as well, and to some extent what Pivotal's and Bob Lee's plans are for @Inject.

      Kind regards,
      Arjan




      On Thu, Oct 25, 2018 at 7:16 PM Scott Kurz <skurz@xxxxxxxxxx> wrote:
          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



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


      --
      Raymond Augé (@rotty3000)
      Senior Software Architect Liferay, Inc. (@Liferay)
      Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)
      _______________________________________________
      ee4j-pmc mailing list
      ee4j-pmc@xxxxxxxxxxx
      To change your delivery options, retrieve your password, or unsubscribe from this list, visit
      https://www.eclipse.org/mailman/listinfo/ee4j-pmc_______________________________________________
      ee4j-pmc mailing list
      ee4j-pmc@xxxxxxxxxxx
      To change your delivery options, retrieve your password, or unsubscribe from this list, visit
      https://www.eclipse.org/mailman/listinfo/ee4j-pmc

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



Back to the top