You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2022/03/22 18:58:00 UTC

[jira] [Closed] (ARTEMIS-3655) isolate the ErrorProne dependencies to the profiles that use them

     [ https://issues.apache.org/jira/browse/ARTEMIS-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-3655.
------------------------------------

> isolate the ErrorProne dependencies to the profiles that use them
> -----------------------------------------------------------------
>
>                 Key: ARTEMIS-3655
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3655
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>    Affects Versions: 2.20.0
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.21.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The build optionally uses ErrorProne during compilation to catch certain issues. The ErrorProne dependency was added as a provided dep to various modules, rather than to the compiler config, as doing so would require consolidation all annotation processing there. However this means that ErrorProne and its number of dependencies inc Guava are present on the path of most modules during the build/tests even when ErrorProne compilation isnt being used.
> This change isolates the dependency to the errorprone profiles, defined only in the parent pom and inherited by the rest of the modules, thus simplifying the config, enabling it in places it was not being enabled before, and ensuring the deps are only present when the compiler is actually being instructed to use them.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)