[JSR358-22] Clarify Compatibility policy Created: 06/Jul/12  Updated: 01/Apr/15

Status: Open
Project: jsr358
Component/s: Compatibility
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: pcurran Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Sun/Oracle have consistently insisted on strong compatibility requirements that prohibit incompatible implementations.

Others argue that incompatible implementations are permissible so long as these do not use the Java name.

Ensure that the JSPA defines a clear policy on compatibility and that this is addressed in any recommended or required licenses.

Should we continue to insist that compatibility is binary, or should we permit incompatible implementations under some circumstances? (E.g. the Transplant JSR proposal from JSR 306.)

Generated at Mon Apr 24 10:08:26 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.