[ 
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964995#comment-16964995
 ] 

Robert Scholte commented on MCOMPILER-320:
------------------------------------------

bq. David has clearly proven that this is necessary...

In the end I need an integration test for it and so far we haven't been able to 
define one. Those that were provided I was able to compile with a different set 
of parameters. So to me it is not that clearly proven.

Everything on the classpath should be managed as a dependency in the pom. Only 
this way Maven can ensure complete classpath resolution (including transitive 
dependencies). So including it in a different is not an option for me, 
excluding by groupId+artifactId in the configuration might be a solution, but 
it is still a codesmell for me. I don't want Maven users to be seduced by a 
parameter the should not need. To me it is still an edge case and AFAIK only 
Redhat needs to trick the compiler, so it does make sense to maintain your own 
fork as done right now.

I've tried to find the problem with Quarkus, but it is simply too big. 


> 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
(v8.3.4#803005)

Reply via email to