Not specifying a plugin version number is interpreted by Maven as "use whatever

fucking arbitrary version you like". Fortunately, it is possible to instruct
Maven to do what would be the sensible default: use the latest release version
of the plugin.

Now that I have done so, the magical insertion of a -link argument for the Java
API is working. Much to my chagrin, the associated <detectLinks> option of the
javadoc plugin is a cruel joke.


git-svn-id: https://samskivert.googlecode.com/svn/trunk@2862 6335cc39-0255-0410-8fd6-9bcaacd3b74c
This commit is contained in:
samskivert
2010-09-09 04:44:52 +00:00
parent 155c8bada1
commit eb4b4b90dd
+5 -1
View File
@@ -82,6 +82,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>RELEASE</version>
<configuration>
<source>1.5</source>
<target>1.5</target>
@@ -112,6 +113,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
<version>RELEASE</version>
<configuration>
<encoding>UTF-8</encoding>
</configuration>
@@ -119,6 +121,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>RELEASE</version>
<configuration>
<excludes>
<exclude>com/samskivert/swing/TestComboButtonBox*</exclude>
@@ -138,11 +141,11 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>RELEASE</version>
<configuration>
<quiet>true</quiet>
<excludePackageNames>com.samskivert.velocity:com.samskivert.xml</excludePackageNames>
<links>
<link>http://download.oracle.com/javase/6/docs/api/</link>
<link>http://java.sun.com/products/javamail/javadocs/</link>
<link>http://download.oracle.com/javaee/1.2.1/api/</link>
</links>
@@ -151,6 +154,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>RELEASE</version>
<executions>
<execution>
<id>sign-artifacts</id>