Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?
So to sum up:

1. There MUST be a LICENSE file in the root folder of the JavaDoc JAR, and
2. The footer MUST link to https://www.eclipse.org/legal/efsl.php 

Or am I missing something?

Ivar

On Thu, Aug 8, 2019 at 9:04 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Read my response again. I think that you may be seeing a "not" that's not there.

I'm pretty sure that we're giving the same answer. 

Wayne

On Thu, Aug 8, 2019 at 2:26 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
You're way, way, way too late to ask for that.  This has been our policy for 20+ years, for the reason I described here and have described previously when people have asked.

If the Eclipse policy is that "products" (e.g., jar files) MUST NOT include the text of the license, we'll need to update all projects for the next release.  If the policy is somehow specific to javadocs, or somehow specific to the EFSL, we'll need to adjust accordingly.


Wayne Beaton wrote on 8/8/19 11:15 AM:
Please do include the text of the license with the Javadoc.

Wayne

On Thu, Aug 8, 2019 at 2:13 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
I can't speak for Eclipse legal, but for Sun/Oracle legal it was always critical to include the license in the "product".  Otherwise the license could (in theory) change after you downloaded and started using the product.  That's why we always included the license in the javadoc bundle.  (Obviously that doesn't solve the problem if you're viewing the javadocs on the jakarta.ee web site.)

Even if the license weren't included, the footer should definitely link to the license.

Scott Stark wrote on 8/8/19 6:05 AM:
In reviewing the BV javadocs, the footer statement is correct, but there is no link to an EFSL license file and there is no EFSL license content in the apidocs tree. Is there a requirement to have a link to a local file? Could we just be using a common external link to the https://www.eclipse.org/legal/efsl.php page? 



_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.


_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec



--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

_______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

Back to the top