Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-stable-dev] About to release Jakartaee-Stable 1.0
Ed,  The release tracker was updated by me.  I assume I can change it to 1.7.1.

I've also talked with Kevin Sutter and we both agree that the versions you list are how we should go.  The only exception is that you listed rpc-api twice.  But from your link I found this:
<javax.management.j2ee-api.version>1.1.2</javax.management.j2ee-api.version>

So managementment-api will be 1.1.3.

Thanks

On Thu, Nov 8, 2018 at 1:23 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Sorry but I'm still a bit confused -- and not likely to do anything you are doing.

In Eclipse GlassFish POM, I read the following:

  • <javax.xml.rpc-api.version>1.1.2</javax.xml.rpc-api.version> (same in eclipse-ee4j)
  • <javax.xml.registry-api.version>1.0.8</javax.xml.registry-api.version> (same in eclipse-ee4j)
  • <javax.enterprise.deploy-api.version>1.7</javax.enterprise.deploy-api.version> (same in eclipse-ee4j)
  • <javax.xml.rpc-api.version>1.1.2</javax.xml.rpc-api.version>

Ideally, each of these would be bumped by the micro increment as follows

  • rpc-api: 1.1.3
  • registry-api: 1.0.9
  • deploy-api: 1.7.1
  • rpc-api: 1.1.3

These seem to align with what's in Maven (plus 0.0.1) now. @m0mus: the Release Tracker shows deploy-api moving to 1.8. Is that what we want? I'd have thought, 1.7.1 (as listed above).

-- Ed


On 11/8/2018 10:47 AM, Jim Krueger wrote:
Some of the links were incorrect and I've made other changes to normalize the versions.

This note declares my intention to release Jakartaee-Stable 1.0.

These are the current Java EE versions of the following projects:

Maven coordinates have changed, but no API changes have been made.

See:

The new Maven coordinates will be:

<groupId>jakarta.enterprise.deploy</groupId>
<artifactId>jakarta.enterprise.deploy-api</artifactId>
<version>1.8</version>

<groupId>jakarta.xml.registry</groupId>
<artifactId>jakarta.xml.registry-api</artifactId>
<version>1.0.1</version>

<groupId>jakarta.xml.rpc</groupId>
<artifactId>jakarta.xml.rpc-api</artifactId>
<version>1.1.4</version>

<groupId>jakarta.management.j2ee</groupId>
<artifactId>jakarta.management.j2ee-api</artifactId>
<version>1.1.3</version>

If there are any objections, please let me know.

Thanks,
Jim Krueger

On Thu, Nov 8, 2018 at 11:34 AM Kevin Sutter <kwsutter@xxxxxxxxx> wrote:
Agree, Ed.  This is what we should be driving for...

Thanks, Kevin

On Thu, Nov 8, 2018 at 11:23 AM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

We should try to use micro as the bump. These values might still need to be evaluated since the prior versions don't seem to be consistent.

  • deploy: 1.7.1
  • jaxr: 1.0.1 (or 1.0.5)
  • jax-rpc: 1.1.1
  • management: 1.1.1 (or 1.1.2)
Thanks,
-- Ed

On 11/8/2018 9:18 AM, Jim Krueger wrote:
This was a point of confusion for me as well Kevin.   The versions listed are the latest in the mvnrepository and the jakarta versions listed are a +1 of whatever was listed in each projects POM.xml.

Perhaps somebody else on this mailing list understands why this occurred?

On Thu, Nov 8, 2018 at 11:15 AM Kevin Sutter <kwsutter@xxxxxxxxx> wrote:
Why are we increasing jaxr-api from 1.0._04 to 1.0.9?  Seems like a large jump.

Same for rpc-api from 1.1.1 to 1.1.3?

And, for management 1.1-rev-1 to 1.1.3?

These increases in versions seems odd to me...

--  Kevin

On Thu, Nov 8, 2018 at 11:05 AM Jim Krueger <jckofbyron@xxxxxxxxx> wrote:
Hi,
This note declares my intention to release Jakartaee-Stable 1.0.

These are the current Java EE versions of the following projects:

Maven coordinates have changed, but no API changes have been made.

See:

The new Maven coordinates will be:

<groupId>jakarta.enterprise.deploy</groupId>
<artifactId>jakarta.enterprise.deploy-api</artifactId>
<version>1.8</version>

<groupId>jakarta.xml.registry</groupId>
<artifactId>jakarta.xml.registry-api</artifactId>
<version>1.0.9</version>

<groupId>jakarta.xml.rpc</groupId>
<artifactId>jakarta.xml.rpc-api</artifactId>
<version>1.1.3</version>

<groupId>jakarta.management.j2ee</groupId>
<artifactId>jakarta.management.j2ee-api</artifactId>
<version>1.1.3</version>

If there are any objections, please let me know.

Thanks,
Jim Krueger
_______________________________________________
jakartaee-stable-dev mailing list
jakartaee-stable-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-stable-dev
_______________________________________________
jakartaee-stable-dev mailing list
jakartaee-stable-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-stable-dev


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

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


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

Back to the top