[
https://issues.apache.org/jira/browse/MNG-5855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705006#comment-14705006
]
Samuel Wu commented on MNG-5855:
--------------------------------
Thank you, Hervé, for investigating the problem and providing the insight.
Mikael Barbero has confirmed that it was his oversight and
f1492191-c1d9-4caa-a6bf-44160486454d.xml is not a toolchain file. I'll run more
test and report back.
I apologize if you found my comment offensive and that was not my intention. It
was not that I didn't trust you. I just don't have the expertise and enough
information to evaluate it. It's basically a conversion between Maven team and
Eclipse team and I'm playing a middle man. I wanted to double check and ensure
that I didn't make the wrong interpretation before I pass the information to
another side.
> 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.7
>
>
> 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)
