[
https://issues.apache.org/jira/browse/GEODE-6611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821428#comment-16821428
]
ASF subversion and git services commented on GEODE-6611:
--------------------------------------------------------
Commit f3428c6e3365323321637961c0f3036ede3b83be in geode's branch
refs/heads/develop from Patrick Rhomberg
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f3428c6 ]
GEODE-6611: Correct publication issues in all-bom. (#3483)
* Add repository specification from publish.gradle to bom publishing
block. This configuration should be extracted in a future commit to
avoid duplication of code. Without this block, the bom publish task
appears always UP-TO-DATE.
* Add signing, also previously in publish.gradle.
* Extra work with scope removed. As a bom without scope will default to
'compile' scope, and as explicit is better than implicit, the extra work
was superfluous.
> 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
(v7.6.3#76005)
