Re: [ee4j-build] Legal Documents within produced artifacts?

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

Yes. The LICENSE and NOTICE files should also be present in the META-INF/ directories of the produced artifacts.

Wayne

On Wed, Sep 19, 2018 at 5:35 PM Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:

Wayne, can you answer it?

— Dmitry

On 19 Sep 2018, at 23:03, Joakim Erdfelt <joakim.erdfelt@xxxxxxxxx> wrote:

(Resubmitting this question now that my subscription is fixed. Apologies if this gets duplicated due to admin actions on the mailing list backend)

Not sure if this is a requirement of the eclipse-ee4j effort, so I'm going to ask.

Per the Eclipse ee4j documentation at https://github.com/eclipse-ee4j/ee4j/wiki/How-to-release-the-first-Eclipse-version-of-projects

The LICENSE and NOTICE files should be present at the root of every source code repository

git.eclipse.org/project.git

 ├── LICENSE

 ├── NOTICE

 └── ...

But something not mentioned in the above doc is another requirement that the Eclipse Foundation has historically had.

See Eclipse Projects Handbook for Legal Docs at https://www.eclipse.org/projects/handbook/#legaldoc

The LICENSE and NOTICE files should also be present in the META-INF/ directories of the produced Artifacts.

MyFile.jar

 ├── META-INF

 │   ├── NOTICE

 │   └── LICENSE

 └── ...

Are we expected to ensure these files are present in the produced Artifacts as well for the eclipse-ee4j efforts?

- Joakim Erdfelt

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build

--

Wayne Beaton

Director of Open Source Projects

The Eclipse Foundation