You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Samuel Wu (JIRA)" <ji...@apache.org> on 2015/07/13 21:26:04 UTC

[jira] [Commented] (MNG-5855) Maven 3.3.3 ignores the customized Toolchain

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

Samuel Wu commented on MNG-5855:
--------------------------------

This eclipse build works well with Maven 3.2.5 and the build started to fail after moving to Maven 3.3.1. The same problem was also found in Maven 3.3.3

> Maven 3.3.3 ignores the customized Toolchain
> --------------------------------------------
>
>                 Key: MNG-5855
>                 URL: https://issues.apache.org/jira/browse/MNG-5855
>             Project: Maven
>          Issue Type: Bug
>          Components: Bootstrap & Build
>    Affects Versions: 3.3.3
>            Reporter: Samuel Wu
>              Labels: patch
>             Fix For: 3.3.4
>
>
> This is an Eclipse build in the Hudson environment. Maven 3.3.3 was used to run the build and a customized Toolchain is defined by --toolchains option. But the customized toolchain location is ignored by Maven and the default user toolchain in the directoy ~/.m2 is always picked up.
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=472084 for more details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)