Okay, so this is solely a trademark topic then, not a technical issue.
Is the current licence contract public? We should link to that licence contract from within the LICENCE file. So all committers know the exact traps they could fall into. In particular if some third party non-Eclipse guy simply forks my private fork of JAX-RS and follows strictly the EPL, he needs to know that the "javax." package suffix is treated as an Oracle trademark, while just the Word "Java" is actually egistered. How should he know?
Thanks for clarification.
-Markus
From: Bill Shannon [mailto:bill.shannon@xxxxxxxxxx]
Sent: Freitag, 5. April 2019 01:37
To: EE4J PMC Discussions; Markus KARG
Subject: 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?
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.
I don't want to be nitpicking but if you want to make it bullet-proof you need to declare what "change" means.
-Markus
A little clarification. See inlined below.
We have updated the PMC statement regarding work on the Jakarta EE Specification 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)
- 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!
_______________________________________________
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
