[
https://issues.apache.org/jira/browse/GEODE-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799381#comment-16799381
]
ASF subversion and git services commented on GEODE-6532:
--------------------------------------------------------
Commit 8fd839e8b73e40bd2dfd14f331b587431bd35a66 in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8fd839e ]
GEODE-6532: Using implementation/api in geode-core instead of compile
* Using implementation or api where appropriate in geode-core
dependencies. This allows downstream consumers of geode-core to get these
dependencies as runtime dependencies instead of compile.
* Adding first order dependencies to other subprojects that needed them.
* Removing a couple of dependencies from geode-core that we were only
using transitively.
* Adding comments to geode-core dependencies
> Convert compile dependencies to implementation/api dependencies
> ---------------------------------------------------------------
>
> Key: GEODE-6532
> URL: https://issues.apache.org/jira/browse/GEODE-6532
> Project: Geode
> Issue Type: Improvement
> Components: build, docs
> Reporter: Patrick Rhomberg
> Assignee: Dan Smith
> Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> The {{compile}} configuration has been deprecated for some time. {{api}}
> will behave similarly, whereas {{implementation}} will appear to be a
> {{runtime}} dependency to consumers.
> This will require examining our public API so that we may correctly declare
> which dependencies are {{api}}. When a PR is made, an email should be sent
> to the dev@ and/or user@ lists warning that those consuming internal APIs
> (against best practice) may experience breakages if their own dependencies
> are not properly declared. Similarly, a release note on this topic could be
> helpful to those upgrading.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
