[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794914#comment-16794914
]
Sanne Grinovero commented on MCOMPILER-320:
-------------------------------------------
Hi [~rfscholte], would be really great to have this merged upstream.
We're having a lot of projects now using the forked plugin version that David
had to create to include this patch; e.g. see
https://github.com/quarkusio/quarkus/issues/1508 but beyond Quarkus this
affects most JBoss projects too.
The good news is that since all these projects have been using it for months,
it has been well tested!
I see the conversation here was that you were quite positive about including
this; then to be fair I don't understand your last question. We for sure need
to be able to build projects for JDK8 still as well.
> 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)
