Re: [jakarta.ee-spec.committee] EFSL in Javadoc?

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

Kevin Sutter wrote on 7/10/19 1:11 PM:

Hi,
On our wiki (https://wiki.eclipse.org/How_to_Prepare_API_Projects_to_Jakarta_EE_8_Release), we indicate that the javadoc should include the EFSL:

• Javadocs should include the Eclipse Foundation Specification License.

But, what about the non-Oracle projects (Batch, BV, CDI)?  These projects are coming in with ASLv2 for their licensing (already approved).  We will leave all of this imported code with ASLv2, correct?

The code should have whatever code license it needs, but the generated javadocs need to use the ESFL license.

And, what about the overall Spec document?  The template contains the EFSL in the front matter.  Should that be replaced for these non-Oracle projects?  Or, does the skeletal Spec document contain the EFSL, while the Javadoc itself has the ASLv2?  A little confusing, but not bad...

The spec document needs the EFSL license as well.  That's the license we're using for the approved specs, independent of the license for the code of any Compatible Implementation.