You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Robert Houghton (Jira)" <ji...@apache.org> on 2021/05/28 18:33:00 UTC

[jira] [Resolved] (GEODE-6611) Subprojects should be audited with respect to which plugins ought be applied

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

Robert Houghton resolved GEODE-6611.
------------------------------------
    Resolution: Fixed

> Subprojects should be audited with respect to which plugins ought be applied
> ----------------------------------------------------------------------------
>
>                 Key: GEODE-6611
>                 URL: https://issues.apache.org/jira/browse/GEODE-6611
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Patrick Rhomberg
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Previously, every Gradle subproject was aggressively configured via blocks like
> {noformat}
> subprojets {
>   apply plugin: 'java'
>   ...
> }
> {noformat}
> As the code base expanded, we have introduced many subprojects who do not warrant a "standard" configuration as a Java project.  For instance, in GEODE-6569, a subproject responsible for producing Geode's BOM was also producing a trivial jar.  This is the direct result of a configuration like the above.
> Modularity was restored by GEODE-6383 and such invasive configuration no longer exists.  We will soon be positioned to remove from such subprojects those plugins that do not belong.
> Each subproject should be audited and only pull in the plugins necessary.  This may resolve many tangental issues, particularly with publication, e.g., the war subproject publishing jars not fit for (direct) consumption.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)