You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Patrick Rhomberg (JIRA)" <ji...@apache.org> on 2019/04/06 20:07:00 UTC
[jira] [Created] (GEODE-6611) Subprojects should be audited with
respect to which plugins aught be applied
Patrick Rhomberg created GEODE-6611:
---------------------------------------
Summary: Subprojects should be audited with respect to which plugins aught be applied
Key: GEODE-6611
URL: https://issues.apache.org/jira/browse/GEODE-6611
Project: Geode
Issue Type: Improvement
Reporter: Patrick Rhomberg
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
(v7.6.3#76005)