[jira] [Created] (OODT-624) maven-javadoc-plugin - request to use a later version (e.g. 2.9)

["Ross Laidlaw (JIRA)" <ji...@apache.org>]

Ross Laidlaw created OODT-624:
---------------------------------

             Summary: maven-javadoc-plugin - request to use a later version (e.g. 2.9)
                 Key: OODT-624
                 URL: https://issues.apache.org/jira/browse/OODT-624
             Project: OODT
          Issue Type: Dependency upgrade
    Affects Versions: 0.6
            Reporter: Ross Laidlaw
            Assignee: Ross Laidlaw
            Priority: Minor
             Fix For: 0.6


When building OODT for the first time after a fresh check-out of the trunk, the maven-javadoc-plugin (v2.7) gets stuck and throws many exceptions like this:

{panel}
[INFO] --- maven-javadoc-plugin:2.7:javadoc (default-cli) @ oodt-commons ---
[INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.7:javadoc' has not be previously called for the project: 'org.apache.oodt:cas-cli:jar:0.6-SNAPSHOT'. Trying to invoke it...
[ERROR] MavenInvocationException: Error when invoking Maven, consult the invoker log file: /usr/local/src/oodt-t/commons/target/invoker/maven-javadoc-plugin1673025036.txt
{panel}

After the Javadocs have all been built individually, everything's fine, but the first time around it gets stuck if invoked from the top-level directory.  It's a known problem with the maven-javadoc-plugin (I think covered by several Codehaus JIRA issues, e.g. [MJAVADOC-275|http://jira.codehaus.org/browse/MJAVADOC-275] and [MJAVADOC-276|http://jira.codehaus.org/browse/MJAVADOC-276]).  It seems to have been fixed from v2.8 onwards, so perhaps we could use the latest version (v2.9).



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira