[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794968#comment-16794968
]
Robert Scholte commented on MCOMPILER-320:
------------------------------------------
I've justed created a new branch, [cherry picking the integration
test|https://github.com/apache/maven-compiler-plugin/commit/32c8298dcc8afc424e08cf067f21f6c150ced7f8]
and [it
succeeds|https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-compiler-plugin/job/MCOMPILER-320_sunmisc/]
without changes to the main code.
Either the integration test is incomplete, or it is already supported with the
current version.
> 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
> 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
(v7.6.3#76005)
