Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Requirements around duplicating spec jars?

John D. Ament wrote on 11/27/17 3:07 PM:
Ok, thanks.  I think this clarifies many of my questions.  A couple minor things below.

On Mon, Nov 27, 2017 at 5:44 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
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).
By "those files" do you mean the files you create based on the specification and that implement the APIs defined in the specification?  Yes, you choose whatever license you want for those files.  Of course, the implementation must meet the requirements in the specification license.


Back to the top