[jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?

From: Scott Stark <starksm64@xxxxxxxxx>
Date: Thu, 8 Aug 2019 06:05:13 -0700
Delivered-to: jakarta.ee-spec@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/jakarta.ee-spec>
List-help: <mailto:jakarta.ee-spec-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec>, <mailto:jakarta.ee-spec-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/jakarta.ee-spec>, <mailto:jakarta.ee-spec-request@eclipse.org?subject=unsubscribe>

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?

Follow-Ups:
- Re: [jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?
  - From: Bill Shannon
- Re: [jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?
  - From: Ivar Grimstad

Prev by Date: Re: [jakarta.ee-spec] [jakartaee-spec-project-leads] PR for org.eclipse.ee4j:project pom
Next by Date: Re: [jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?
Previous by thread: [jakarta.ee-spec] PR for org.eclipse.ee4j:project pom
Next by thread: Re: [jakarta.ee-spec] Does the EFSL license need to be in the javadocs dist?
Index(es):
- Date
- Thread

Breadcrumbs