You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/02/25 18:57:18 UTC

[jira] [Updated] (GEODE-818) RC Feedback: Fix Maven & pom dependencies

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

Anthony Baker updated GEODE-818:
--------------------------------
    Fix Version/s: 1.0.0-incubating.M2

> RC Feedback: Fix Maven & pom dependencies
> -----------------------------------------
>
>                 Key: GEODE-818
>                 URL: https://issues.apache.org/jira/browse/GEODE-818
>             Project: Geode
>          Issue Type: Task
>    Affects Versions: 1.0.0-incubating.M1
>            Reporter: Nitin Lamba
>             Fix For: 1.0.0-incubating.M2
>
>
> Maven and POM dependencies are too many for simple
> From [~niall.pemberton@btinternet.com]:
> If I'm building a gemfire client and depend on gemfire-core, do I really need all those dependencies? Do I always need them for a gemfire member? Looks to me like some of them should be "optional" or "provided" - especially some of the logging stuff.
> * Spring Framework only referenced in CLI & Web, except XmlEntity (uses org.springframework.util.Assert) and PdxInstanceImpl (uses org.springframework.util.StringUtils)
> * SequenceFile only class to directly reference commons-logging
> * commons-lang only used in hdfs & CLI
> * javax.mail only used in MailManager
> * Jetty only referenced by ManagementAgent & RestAgent, except for CumulativeNonDistinctResults
> * Netty only referenced in the redis package
> * Can't find any reference to slf4j



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)