[jira] [Created] (MJAVADOC-647) Support for Split jdk 7 during build

["Jeremy Landis (Jira)" <ji...@apache.org>]

Jeremy Landis created MJAVADOC-647:
--------------------------------------

             Summary: Support for Split jdk 7 during build
                 Key: MJAVADOC-647
                 URL: https://issues.apache.org/jira/browse/MJAVADOC-647
             Project: Maven Javadoc Plugin
          Issue Type: Dependency upgrade
          Components: javadoc
    Affects Versions: 3.2.0
            Reporter: Jeremy Landis


Currently it is possible to split the source / test code to compile differently.  Example use case is requirement to cross compile source target to jdk 7 and test with jdk 8.  This works fine, but the javadoc plugin doesn't seem to handle this very well. The moment java 8 items such as lambdas are introduced, it fails on javadoc generation on test side only.  I'm not sure how the pre java 9 setup is, but the post java 9 setup seems to rely only on maven.compiler.release and it should also take into account maven.compiler.testRelease.  Is it possible to have this added?

 

I am working around this by forcing the higher javadoc solution directly on the plugin configuration.  My preference is to not have to make special overrides when the simple flags suffice.

 

So for java 9+, asking that this handles

 

<maven.compiler.release>${java.release.version}</maven.compiler.release>
 <maven.compiler.testRelease>${java.test.release.version}</maven.compiler.testRelease>

 

properly.

 

I suspect although didn't see in the source, that for java 8 or earlier it is either using something on its own or somehow relying on the old source/target settings but doesn't use the test variation during test java doc creation.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)