[jira] (MPJAVADOC-55) Allow reinitialisation of sourcepath from maven.compile.source.set

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MPJAVADOC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MPJAVADOC-55.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Allow reinitialisation of sourcepath from  maven.compile.source.set
> -------------------------------------------------------------------
>
>                 Key: MPJAVADOC-55
>                 URL: https://jira.codehaus.org/browse/MPJAVADOC-55
>             Project: Maven 1.x Javadoc Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.7
>         Environment: Windows XP, jdk 1.4.1-b21, maven 1.02
>            Reporter: Achim Westermann
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> The first time the plugin is loaded, it passes the maven.compiler.src.set into an internal ant path. 
> Further invocations of the plugin will not do this again. 
> More complex builds could do several checkouts and incremental builds (core, then extensions...) 
> with separate javadoc outputs. 
>     <ant:path 
>       id="src-modules"
>       location="${maven.scm.checkout.dir}/src-modules"
>     />
>     <maven:addPath
>       id="maven.compile.src.set"
>       refid="src-modules"
>     />
> may be used to add new paths for the maven-java-plugin and it works: 
> The new paths are taken into account even if java:compile is invoked 
> several times during a single maven run. 
> Javdoc fails to take the new paths. 
> Couldn't you just wrap the initalisation to a goal and just call it as a prereq from 
> generate? Or peek at the java plugin. That would be great. 
> kind regards, 
> Achim



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)