You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-commits@incubator.apache.org by ma...@apache.org on 2007/02/14 09:37:45 UTC
svn commit: r507451 -
/incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/pom.xml
Author: matzew
Date: Wed Feb 14 01:37:44 2007
New Revision: 507451
URL: http://svn.apache.org/viewvc?view=rev&rev=507451
Log:
trying a suggested work around for a maven-source-plugin bug
Modified:
incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/pom.xml
Modified: incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/pom.xml
URL: http://svn.apache.org/viewvc/incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/pom.xml?view=diff&rev=507451&r1=507450&r2=507451
==============================================================================
--- incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/pom.xml (original)
+++ incubator/adffaces/tags/maven-plugin-parent-1.0.0-incubating/pom.xml Wed Feb 14 01:37:44 2007
@@ -278,7 +278,7 @@
</execution>
</executions>
</plugin>
- <plugin>
+ <!--plugin>
<artifactId>maven-source-plugin</artifactId>
<version>2.0.2</version>
<executions>
@@ -289,7 +289,37 @@
</goals>
</execution>
</executions>
- </plugin>
+ </plugin-->
+ <plugin>
+ <!-- This should possibly better be done by using a resource
+ definition. However, if we declare a resource with
+ ${basedir} as the base directory, then the
+ maven-source-plugin will add the whole directory to
+ its contents.
+ -->
+ <artifactId>maven-antrun-plugin</artifactId>
+ <executions>
+
+ <execution>
+ <phase>generate-resources</phase>
+ <configuration>
+ <tasks>
+ <copy todir="${project.build.outputDirectory}/META-INF">
+ <fileset dir="${basedir}">
+ <include name="LICENSE.txt" />
+ <include name="NOTICE.txt" />
+
+ </fileset>
+ </copy>
+ </tasks>
+ </configuration>
+ <goals>
+ <goal>run</goal>
+ </goals>
+ </execution>
+
+ </executions>
+ </plugin>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.2</version>