[
http://jira.codehaus.org/browse/MJAVADOC-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=143854#action_143854
]
Benjamin Bentmann commented on MJAVADOC-211:
--------------------------------------------
>From {{AbstractJavadocMojo.java:1471}}
{code:java}
// ----------------------------------------------------------------------
// Javadoc output directory as File
// ----------------------------------------------------------------------
File javadocOutputDirectory = new File( getOutputDirectory() );
if ( javadocOutputDirectory.exists() && !javadocOutputDirectory.isDirectory() )
{
throw new MavenReportException( "IOException: " + getOutputDirectory() + "
is not a directory." );
}
if ( javadocOutputDirectory.exists() && !javadocOutputDirectory.canWrite() )
{
throw new MavenReportException( "IOException: " + getOutputDirectory() + "
is not writable." );
}
javadocOutputDirectory.mkdirs();
{code}
i.e. there is already a call to {{mkdirs()}. So I wonder whether this issue was
really present or just a side effect of the (still present) failures with RC4.
> create the report output directory if it doesn't exist
> ------------------------------------------------------
>
> Key: MJAVADOC-211
> URL: http://jira.codehaus.org/browse/MJAVADOC-211
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.5
>
>
> currently, the javadoc report relies on maven to have created the reporting
> base directory first. This need not be the case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
