[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978626#comment-16978626
]
Ken Finnigan commented on MCOMPILER-320:
----------------------------------------
[~rfscholte] I tried implementing your PR to [~gunnar.morling] repo and I
couldn't get it to add a JDK 9 class as a dependency to the JDK 11 compile with
just the `multiRelease=true` flag.
Is there a way to adjust the classpath to include previously compiled classes
for specific JDKs? Such that a JDK 11 specific class can use a JDK 9 specific
class.
> Allow additional class path items to be given during compilation
> ----------------------------------------------------------------
>
> Key: MCOMPILER-320
> URL: https://issues.apache.org/jira/browse/MCOMPILER-320
> Project: Maven Compiler Plugin
> Issue Type: New Feature
> Reporter: David M. Lloyd
> Assignee: Robert Scholte
> Priority: Major
>
> At present it is very difficult to include additional class path items during
> compilation that are not dependencies. But this is a very useful capability,
> especially when doing partial builds, MR JARs, JDK API stubbing, including
> dependency items that cannot be included in any other build phase or
> execution, etc.
> This enhancement and pull request are to request the addition of a
> {{additionalCompilePathItems}} property in CompilerMojo or
> AbstractCompilerMojo which includes additional filesystem paths in the
> compilation class path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
