You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/11/08 19:33:06 UTC

[jira] [Commented] (MNG-6475) Remove guava dependencies

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

Hudson commented on MNG-6475:
-----------------------------

Build failed in Jenkins: Maven TLP » maven » MNG-6012-Missing-Profile-At-End #16

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6012-Missing-Profile-At-End/16/

> Remove guava dependencies
> -------------------------
>
>                 Key: MNG-6475
>                 URL: https://issues.apache.org/jira/browse/MNG-6475
>             Project: Maven
>          Issue Type: Task
>    Affects Versions: 3.6.0
>            Reporter: Phillip Webb
>            Assignee: Karl Heinz Marbaise
>            Priority: Trivial
>             Fix For: 3.6.0
>
>
> It looks like [this commit|https://github.com/apache/maven/commit/b8c06e61ab73cd9e25a5b2c93d9e5077b2196751] removed Guava imports from the codebase, however, several dependencies are still declared in the POMs. This can be problematic for projects that embed Maven jars (see MNG-6306 for an example).
> I tried a local Maven build with guava dependencies removed and it appears to compile without issue. I'll submit a pull request with the relevant changes.



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