[jira] [Commented] (INFRA-10648) Jenkins build fails with Maven (latest) but runs with Maven 3.1.1

["Geoffrey Corey (JIRA)" <ji...@apache.org>]

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

Geoffrey Corey commented on INFRA-10648:
----------------------------------------

[~abayer] and ideas?

> Jenkins build fails with Maven (latest) but runs with Maven 3.1.1
> -----------------------------------------------------------------
>
>                 Key: INFRA-10648
>                 URL: https://issues.apache.org/jira/browse/INFRA-10648
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: Maven (latest) 
> https://builds.apache.org/job/ODFToolkit-windows/95/injectedEnvVars/
>            Reporter: Svante Schubert
>
> There is build issues on our Apache Windows server when using the latest Maven version. The exception 
> Caused by: java.lang.IllegalAccessError: class com.google.common.collect.AbstractMapBasedMultimap cannot access its superclass com.google.common.collect.AbstractMultimap
> seem similar to a Jenksin/Maven3.2.1 bug.
> https://issues.jenkins-ci.org/browse/JENKINS-22252
> The build works with Maven 3.1.1.
> I did a build test of three Windows builds, where I only exchanged the Maven version:
> https://builds.apache.org/job/ODFToolkit-windows/94 - SUCESSS with Maven 3.1.1 and all updates
> https://builds.apache.org/job/ODFToolkit-windows/95 - FAILS with changing to Maven 3 (latest)
> https://builds.apache.org/job/ODFToolkit-windows/96 - SUCESSS with changing back to Maven 3.1.1
> My full error log can be found at
> https://builds.apache.org/job/ODFToolkit-windows/95/consoleText
> Unfortunately I could not find out what was the latest Maven that causes the action from the environment:
> https://builds.apache.org/job/ODFToolkit-windows/95/injectedEnvVars/



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