John D. Ament wrote on 11/25/17 10:51
AM:
As I understand it, implementations are required to provide
their own set of spec jars for each specification under Java
EE. Will this practice continue under the to-be-named
project?
Under current JCP rules, implementations are not required to
"provide their own set of spec jars".
An independent implementation will provide its own class
files for the javax.* classes.
Yes, this is the requirement I was pointing to. Thanks for clarifying it.
An implementation can choose to depend on "API jar files" (where
they exist) from the reference implementation as a third party
dependency, under the terms of the open source license for the
reference implementation.
So... that makes it much clearer actually. But if I choose to not depend on the RI, can I license those files under another open source license? Assuming that they pass a sigtest only, and don't include javadocs from the RI. E.g. it's not a fork, but provides the same API (clean room implementation, for what its worth).
An implementation can choose to fork the source code of the
reference implementation and provide modified versions of the API
classes, under the terms of the open source license for the
reference implementation.
Of course, in all cases, the implementation must pass the TCK.
I can't speak to what rules might exist for the future EE4J
specification process.
