[GEODE-818] Clean up the dependencies of geode-core by moving non-core features to subprojects

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0-incubating.M1
• Assignee: Dan Smith
• Reporter: Nitin Lamba
• Created: 20/Jan/16 20:51
• Updated: 31/May/16 06:34
• Resolved: 20/Jan/16 20:51

Description

Maven and POM dependencies are too many for simple

From [e-mail]:

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

Issue Links

• relates to: GEODE-27 Apache Geode POM file(s) are incorrect!
• mentioned in: Page Loading...

Sub-Tasks

• Remove MailManager and javax.mail dependency: Closed
• Move HDFS code to it's own subproject and get rid of HDFS dependencies in gemfire-core: Closed
• Move redis to it's own sub-project, remove dependencies from core: Resolved
• Move gfsh classes into their own sub project: Open
• Move Admin REST API code into the geode-web project: Closed
• Move JettyHelper and related classes to a subproject: Open