Ok. I have checked in this merge. The subprojects are now named geode-. This affects the directory names in your checkout, as well as the names of the maven artifacts. Additionally, gemfire-core-dependencies.jar is now called geode-dependencies.jar.
See GEODE-917 for additional details. -Dan On Fri, Feb 19, 2016 at 1:51 PM, Nitin Lamba <ni...@ampool.io> wrote: > +1 > > Agree with Anthony - all the artifacts in the /lib directory still read > 'gemfire-XXX.jar'. If renaming is simple enough, it should be picked-up as > part of this change. > > Nitin > > ________________________________________ > From: Anthony Baker <aba...@pivotal.io> > Sent: Friday, February 19, 2016 1:43 PM > To: dev@geode.incubator.apache.org > Subject: Re: [DISCUSS] Merging of feature/GEODE-917 - renaming artifacts > to geode- > > Thanks for testing this out Dan! Downstream project integrations will > need to update maven artifact ID’s. > > Another part of this changeset is renaming ‘gemfire-core-dependencies.jar’ > to ‘geode-dependencies.jar’. > > > +1 > > Anthony > > > On Feb 19, 2016, at 12:01 PM, Dan Smith <dsm...@pivotal.io> wrote: > > > > I'd like to merge in the changes for GEODE-917. This will rename all of > the > > subdirectories to be geode-XXX instead of gemfire-XXX. > > > > It will also change the maven artifacts to be geode-XXX once this change > is > > merged. > > > > Any objections? A review of all of the diffs is a bit annoying, but I > > attached a diff to the ticket that shows the changes other than the > renames: > > > > https://issues.apache.org/jira/secure/attachment/12788739/GEODE-917.diff > > > > -Dan > >
