[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329312#comment-16329312
]
Robert Scholte commented on MCOMPILER-320:
------------------------------------------
Hi David,
I think it would already help if there was an example attached to better
understand what you're trying to achieve (and which we can translate to an
integration test).
My first concern is that you will loose control over the order of the
classpath. I'd prefer to see a solution where the issue is solved with
dependencies, which might require a new scope.
In the end a dependency is just a reference to a file, like all entries on the
classpath, so I would expect there's a more elegant way to solve this.
> 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)
