[
https://issues.apache.org/jira/browse/NIFI-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150995#comment-15150995
]
Sean Busbey commented on NIFI-1520:
-----------------------------------
The wars look like they have actual content.
We can customize the LICENSE/NOTICE that end up in the javadoc jar by placing
them in {{src/main/javadoc/META-INF/}} for the module and the following use of
the resources plugin:
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<executions>
<execution>
<id>license-javadocs</id>
<phase>prepare-package</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/apidocs</outputDirectory>
<resources>
<resource>
<directory>src/main/javadoc/META-INF/</directory>
<targetPath>META-INF/</targetPath>
<includes>
<include>LICENSE</include>
<include>NOTICE</include>
</includes>
<filtering>true</filtering>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
{code}
If there's a common parent pom for the war's this is obviously easier.
In HBase, we only run this part of the plugin when the {{apache-release}}
profile is active, so that it's done during RC making but not otherwise.
> Evaluate/Fix LICENSE/NOTICE entries on Javadoc/Sources bundles
> --------------------------------------------------------------
>
> Key: NIFI-1520
> URL: https://issues.apache.org/jira/browse/NIFI-1520
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 0.5.0
> Reporter: Joseph Witt
>
> Sean Busbey NiFi 0.5.0 RC3 finding:
> ---
> * several -source and -javadoc jars contain improper LICENSE/NOTICE files
> (they cover things "in the binary artifact" that are not in the artifact
> containing the LICENSE/NOTICE file)
> ex:
> * -source and -javadoc for war packaging
> * -source for nar packaging
> --
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
