Thanks, good clarification Jake. Anthony
> On May 11, 2015, at 1:54 PM, Jacob Barrett <[email protected]> wrote: > > Parent POMs should only be used by children projects and not by some external > project as direct dependency. That sort of thing should be left to a BOM type > POM. A Geode Framework BOM would define all the dependencies needed for Geode > to run but wouldn’t include all the sub projects of the parent as some may > not be applicable, like Hydra or something. > > — > > Jacob Barrett > > Enterprise Architect > > Pivotal > > > > > [email protected] > > 503-533-3763 > > On Mon, May 11, 2015 at 1:36 PM, Anthony Baker (JIRA) <[email protected]> > wrote: > >> Anthony Baker created GEODE-22: >> ---------------------------------- >> Summary: Create a parent POM >> Key: GEODE-22 >> URL: https://issues.apache.org/jira/browse/GEODE-22 >> Project: Geode >> Issue Type: Improvement >> Components: build >> Affects Versions: 1.0.0.0-incubating >> Reporter: Anthony Baker >> Assignee: Mark Bretl >> Priority: Minor >> Currently we export these maven artifacts: >> * gemfire-core >> * gemfire-jgroups >> * gemfire-joptsimple >> * gemfire-json >> We should create a parent POM so that a user could simply create a >> dependency on "geode" and not each of the above artifacts. >> -- >> This message was sent by Atlassian JIRA >> (v6.3.4#6332)
