From eb4b4b90dd9b5b6c8453d61311a9fb4408513f33 Mon Sep 17 00:00:00 2001 From: samskivert Date: Thu, 9 Sep 2010 04:44:52 +0000 Subject: [PATCH] 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 option of the javadoc plugin is a cruel joke. git-svn-id: https://samskivert.googlecode.com/svn/trunk@2862 6335cc39-0255-0410-8fd6-9bcaacd3b74c --- pom.xml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 458f9272..402bd1a9 100644 --- a/pom.xml +++ b/pom.xml @@ -82,6 +82,7 @@ org.apache.maven.plugins maven-compiler-plugin + RELEASE 1.5 1.5 @@ -112,6 +113,7 @@ org.apache.maven.plugins maven-resources-plugin + RELEASE UTF-8 @@ -119,6 +121,7 @@ org.apache.maven.plugins maven-surefire-plugin + RELEASE com/samskivert/swing/TestComboButtonBox* @@ -138,11 +141,11 @@ org.apache.maven.plugins maven-javadoc-plugin + RELEASE true com.samskivert.velocity:com.samskivert.xml - http://download.oracle.com/javase/6/docs/api/ http://java.sun.com/products/javamail/javadocs/ http://download.oracle.com/javaee/1.2.1/api/ @@ -151,6 +154,7 @@ org.apache.maven.plugins maven-gpg-plugin + RELEASE sign-artifacts