maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Gastaldi (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MCOMPILER-320) Allow additional class path items to be given during compilation
Date Fri, 01 Nov 2019 15:00:12 GMT

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

George Gastaldi commented on MCOMPILER-320:
-------------------------------------------

[~rfscholte] I don't get why this issue is closed as Won't fix and the reluctance in merging
[https://github.com/apache/maven-compiler-plugin/pull/1] .

David has clearly proven that this is necessary and this parameter has existed in our forked
compiler plugin for years now and it works great for our use cases. It shouldn't impact any
existing behavior. What else do you need? 

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

Mime
View raw message