[jira] [Commented] (GEODE-6532) Convert compile dependencies to implementation/api dependencies

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067349#comment-17067349 ] 

ASF subversion and git services commented on GEODE-6532:
--------------------------------------------------------

Commit 813b76196c279f8eeeaf146cf102883181939c27 in geode-examples's branch refs/heads/develop from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode-examples.git;h=813b761 ]

GEODE-6532: Dependency changes to examples related to the Geode fix. (#92)

Several transitive dependencies will be marked 'runtime' not 'compile'
in the POM from geode, causing examples to not miss symbols. Declare
those dependencies outright.

(cherry picked from commit e974408674428770c35be3b444e022d2b9f1973e)


> 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
>             Fix For: 1.9.0, 1.13.0
>
>          Time Spent: 5.5h
>  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
(v8.3.4#803005)