incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Meschberger <>
Subject Re: Good examples of licensing in ASF produced web apps?
Date Sat, 27 May 2017 11:47:13 GMT
Hi Roman

As has been mentioned by others, I would not think there is any relaxation. At the end of
the day, it is something we build and distribute. So not having appropriate LICENSE and NOTICE
(and probably DEPENDENCIES) is a no-go.

Having said that: The default Maven WAR plugin is just bundling the transitive clousure dependencies
of the project, which if you don’t pay attention is half of the internet. JAR hell live.

Apache Sling also distributes WAR files. The difference here is that it is built with a custom-built
plugin because essentially Sling only uses the servlet container as a container and manages
its own deployment through an OSGi framework.

For example


Am 26.05.2017 um 23:49 schrieb Roman Shaposhnik <<>>:


I advising a podling on producing a binary release that
includes a Java web app (think war file). I wanted to give
them a taste of what TLPs do so I went to the ones that
I knew were generating war files: Oozie and Ranger.
You know the stuff I'm familiar with in Hadoop ecosystem.

What he discovered may shock you! No, but seriously.

Here's what these projects publish on Maven central:

Each of these WAR files:
  1. bundles all sorts of dependancies -- not just the bits coming
   from the project itself

   2. Neither provides a meanigful LICENSE nor NOTICE files.
   The ones under ./WEB-INF/classes/META-INF are stock ones
   and really don't address the binary dependencies bundling

Have we somehow relaxed the requirements for binary artifacts?
I hope not -- and if not -- what are the good examples of web app
projects doing it right?


To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message