Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Updated PMC Statement for work on Jakarta EE Specification Projects
Eclipse is not licensed to create packages in the javax.* namespace.

I can't say for sure that the signature tests would catch such an addition, but it's clear that such a package would not be defined by the JAX-RS spec, nor any other spec, and thus would violate the compatibility rules.

Markus KARG wrote on 4/4/19 12:56 PM:

Why is it "incompatible" if there is a new "sub-package" like  "javax.ws.rs-api.xxx" added alongside the existing ones?

 

From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Bill Shannon
Sent: Donnerstag, 4. April 2019 20:26
To: EE4J PMC Discussions; Ivar Grimstad
Subject: Re: [ee4j-pmc] Updated PMC Statement for work on Jakarta EE Specification Projects

 

Yes, anything that would make it incompatible with the corresponding Java EE specification.

Ivar Grimstad wrote on 4/4/19 10:21 AM:

Somebody will probably correct me here, but my understanding of "change" in this context is:

 

- adding/removing or changing signatures of exposed methods in existing classes/interfaces

- adding/removing packages

 

I guess, anything except fixing bugs at this point.

 

Ivar

 

On Thu, Apr 4, 2019 at 6:41 PM Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

I don't want to be nitpicking but if you want to make it bullet-proof you need to declare what "change" means.

-Markus

 

 

From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Ivar Grimstad
Sent: Donnerstag, 4. April 2019 08:36
To: EE4J PMC Discussions
Subject: Re: [ee4j-pmc] Updated PMC Statement for work on Jakarta EE Specification Projects

 

A little clarification. See inlined below.

 

Ivar

 

On Tue, Apr 2, 2019 at 2:58 PM Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote:

Hi,

 

We have updated the PMC statement regarding work on the Jakarta EE Specification projects.

 

Summed up, the projects:

- Must be able to release a Jakarta EE 8 artifact (minimal changes from the previous release) 

- Must be able to merge the Jakarta EE 8 related changes into the master branch after release

- Must NOT publicly publish SNAPSHOTs or other releases that include the javax.* namespace (yet)

 

The last item should be 

 - Must NOT publicly publish SNAPSHOTs or releases that change the javax.* namespace.

 

 

Apart from the above, the development of new features is good to go!

 

Read the entire PMC statement: https://www.eclipse.org/ee4j/news/?date=2019-04-02 

 

Ivar

_______________________________________________
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