[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825389#comment-16825389
]
David M. Lloyd commented on MCOMPILER-320:
------------------------------------------
Overall I'm quite baffled by the amount of resistance this patch has gotten.
It very clearly solves a problem (multiple problems in fact) for me, the
submitter. It adds flexibility and capability, costs almost nothing to
implement (myself having done this work already) or to maintain, and nobody
would be forced to use it who does not want to. It seems that the main problem
is that you do not think I should be doing the things that I think I should be
doing. Am I wrong?
> 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
(v7.6.3#76005)
