Please include license files

[msimacek]

Both ASL and EPL licenses require the full license texts to be distributed alongside the software. Please include them in the source repository.

[joakime]

This toolchain project is a collection of separate builds for mostly for internal artifacts that are not distributed (in the traditional sense).

This repository really should be split up into multiple separate git repos.

Are there some specific artifacts that are missing these license files?
If so, then we need to correct for that specific artifact.

[msimacek]

I maintain jetty package for Fedora and Fedora requires everything to be built from source, including build-only dependencies. So I have to redistribute those artifacts in order to be able to build jetty.

Are there some specific artifacts that are missing these license files?

Well, all of them (except jetty-distribution-remote-resources). I'm currently interested in jetty-setuid and jetty-test-helper. I can submit a pull request if you want.

[sbordet]

Then we need to update the POMs with the license plugin.

[aslaski]

Hi Simone!
Greetings from Atlassian

My project depends on apache-jsp, which depends on jetty-schemas. For legal reasons licenses for all our dependencies must be explicitly stated. Can you help with this?

Regards,
Adam

[joakime]

@aslaski we are preparing the 9.4.13 release, I'll make sure these 3 artifacts have the appropriate LICENSE and NOTICE files:

• jetty-schemas (see #15)
• jetty-setuid (see #16)
• jetty-test-helper (see #17)

[joakime]

@aslaski jetty-schemas 3.1.1 and 4.0.2 are now on maven central.

[joakime]

Also, @aslaski know that the licenses are declared in the pom, which is in the JAR already, and is a requirement to for any artifact (with source) to exist on maven central.

All other requests for LICENSE / NOTICE will be handled in other issues.

[aslaski]

Many thanks @joakime