Now for the fun part :-) The taglib plugin can't be used without some amount of work (the processing of .tag and .tagx files is off). Until we can un-inherit the plugin, we'll point it to a non-standard location, say src/main/tld and generate the TLD there (all the tag files nested in the default location -- src/main/resources/META-INF -- cause processing issues for the plugin reports as things stand).
git-svn-id: https://svn.apache.org/repos/asf/jakarta/taglibs/proper/rdc/trunk@733376 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/taglibs-rdc/pom.xml b/taglibs-rdc/pom.xml
index 7a2ec68..542ee6b 100644
--- a/taglibs-rdc/pom.xml
+++ b/taglibs-rdc/pom.xml
@@ -77,7 +77,43 @@
<build>
<!-- taglibs-parent has non-standard source dir -->
<sourceDirectory>src/main/java</sourceDirectory>
+ <resources>
+ <!-- The TLD is generated to src/main/tld otherwise the taglib plugin
+ picks up an 'unknown' taglib (see <reporting> below), so we have
+ this otherwise redundant resources section -->
+ <resource>
+ <directory>src/main/tld</directory>
+ <targetPath>META-INF</targetPath>
+ <includes>
+ <include>taglibs-rdc.tld</include>
+ </includes>
+ </resource>
+ <resource>
+ <directory>.</directory>
+ <targetPath>META-INF</targetPath>
+ <includes>
+ <include>NOTICE.txt</include>
+ <include>LICENSE.txt</include>
+ </includes>
+ </resource>
+ <resource>
+ <directory>src/main/resources</directory>
+ <targetPath>.</targetPath>
+ </resource>
+ </resources>
</build>
+ <reporting>
+ <plugins>
+ <plugin>
+ <groupId>net.sourceforge.maven-taglib</groupId>
+ <artifactId>maven-taglib-plugin</artifactId>
+ <configuration>
+ <taglib.src.dir>src/main/tld</taglib.src.dir>
+ </configuration>
+ </plugin>
+ </plugins>
+ </reporting>
+
</project>
