You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hendrik Schreiber (JIRA)" <ji...@apache.org> on 2019/04/23 07:54:00 UTC
[jira] [Commented] (MCOMPILER-320) Allow additional class path
items to be given during compilation
[ https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823790#comment-16823790 ]
Hendrik Schreiber commented on MCOMPILER-320:
---------------------------------------------
Hi,
it sounds like the solution of this bug depends on providing a suitable *integration test that fails* before the solution is applied.
David: Would you still be willing to supply such a test or (if you believe your test already delivers this) point out why Robert wasn't able to reproduce the failure?
I'd love to get my hands on a released 3.8.1 (not for this feature) and this seems to be the last major roadblock.
Thank you.
> 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)