Does it really matter if the incomplete poms are Apache projects? We've
already got all the legal stuff necessary for those.
Elliot Metsger wrote:
Yes, the plugin is cool, but Pluto too uses artifacts that have
incomplete POMs, which results in a incomplete/inaccurate NOTICE file.
Those problems won't go away by themselves of course as the POM for
Xerces 2.6.2 is unlikely to change.
This product includes software, Unnamed -
xerces:xmlParserAPIs:jar:2.6.2, developed
by
$project.organization.name ($project.organization.url).
This product includes software, Unnamed -
commons-logging:commons-logging-api:pom:1.1, developed
by
$project.organization.name ($project.organization.url).
Will have to figure out what to do....
Elliot
Ate Douma wrote:
Elliot Metsger wrote:
So I got pinged again by the repository folks, this time Daniel Kulp.
None of our maven artifacts have a LICENSE or NOTICE file in them, and
apparently this is also required per
http://www.apache.org/legal/src-headers.html:
Does the policy apply to binary/object files, such as executables or
JAR files?
Yes. Even if there are no source files within the release, the
LICENSE file and NOTICE file are still both required within every ASF
distribution -- whether the unit of distribution is a .jar, .msi,
.tar/.?gz, .zip, .exe installer, or any other file format used for
distributions. For example, Windows .exe files must not be used as a
unit of distribution unless they are installers and include the
LICENSE and NOTICE files in their installation.
This is in Jira as PLUTO-349.
Elliot,
Not sure if this is going to work for Pluto but I've tried out the new
(Alpha) maven-remote-resources-plugin for Jetspeed-2.
Its purpose is exactly doing this: adding the Apache NOTICE and
LICENSE files to all artifacts.
It automatically downloads the Apache LICENSE as well as *generates* a
NOTICE file based upon all the dependencies used.
Now, its still in an Alpha state and not (yet) working 100% for
Jetspeed-2 as it depends on the dependencies providing a proper
pom.xml itself.
As Jetspeed-2 uses "bad" dependencies this results in a not fully
satifactory NOTICE file, but maybe for Pluto this might work out just
fine.
Using the plugin is just a matter of putting the following in the main
(parent) pom.xml and you're set:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-remote-resources-plugin</artifactId>
<version>1.0-alpha-4</version>
<executions>
<execution>
<goals>
<goal>process</goal>
</goals>
<configuration>
<resourceBundles>
<resourceBundle>org.apache:apache-jar-resource-bundle:1.0</resourceBundle>
</resourceBundles>
<properties>
<addLicense>true</addLicense>
</properties>
</configuration>
</execution>
</executions>
</plugin>
Regards,
Ate
I'm not sure where this leaves us with our existing releases.
Elliot
