You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2019/01/11 09:34:00 UTC

[jira] [Commented] (MINVOKER-245) Using an alternate toolchain file

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

Robert Scholte commented on MINVOKER-245:
-----------------------------------------

Improvement done in [7c70e76c4fc7e1cf6e2eeb460deb39a1b10b4def|https://gitbox.apache.org/repos/asf?p=maven-invoker-plugin.git;a=commit;h=7c70e76c4fc7e1cf6e2eeb460deb39a1b10b4def]
[~olamy] I've added a selector called {{invoker.toolchain}} to control if the invoker should be executed or not, based on the type and provides values. I guess this should solve the root cause of this issue. 
I wonder if it makes sense to provide an alternative toochain file, it is very related to the running environment, just like the version of jre, maven and the os.


> Using an alternate toolchain file
> ---------------------------------
>
>                 Key: MINVOKER-245
>                 URL: https://issues.apache.org/jira/browse/MINVOKER-245
>             Project: Maven Invoker Plugin
>          Issue Type: Improvement
>            Reporter: Olivier Lamy (*$^¨%`£)
>            Assignee: Olivier Lamy (*$^¨%`£)
>            Priority: Major
>             Fix For: 3.1.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)