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

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

Believe me: I don't like to disappoint people that are trying to improve 
things, but I need to evaluate every PR.  If I would have accepted every PR or 
implement every proposal, this project would be total chaos. For every issue 
I'm trying to understand why is should be added, or think of a solution that 
fits better in the way people are used to work with Maven. In this case I tried 
to come up with a proposal that should be more natural. In general I believe 
dependencies should be made explicit so Maven can resolve them at the right 
time, they should not be part of the configuration-part of a plugin (unless 
there's really no other solution). Based on the response it looks to me like it 
is not a compiling issue and I should not expect any more details since 
everything was already said. I could wait another couple of months, but that 
wouldn't change a thing, hence I decided to close it.
How to solve this? Try to break my integration test. Running examples make it 
often much clearer instead of having to re-read the whole issue over and over 
again.



> 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)

Reply via email to