Re: How to add a new feature into main project?

Adding a new sub-project requires a few build related changes (settings.gradle, geode-assembly/build.gradle, …). You can take a look at geode-common for an example. A great place to begin would be to start a discussion on this list to propose your addition and gather consensus. Anthony > On

How to add a new feature into main project?

Hi All, How to add a new feature like a extended module into the main geode project? thank you very much! theseus yang -- View this message in context: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/How-to-add-a-new-feature-into-main-project-tp7022.html Sent from the

How to add a new feature into main project?

Hi All, How to add a new feature like a extended module into the main geode project? thank you very much! -- View this message in context: http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/How-to-add-a-new-feature-into-main-project-tp7021.html Sent from the Apache Geode

Re: Review Request 49667: GEODE-1631: Removing a hardcoded apache-geode from location

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49667/#review140905 --- Ship it! Ship It! - Darrel Schneider On July 5, 2016, 4:58

Review Request 49667: GEODE-1631: Removing a hardcoded apache-geode from location

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49667/ --- Review request for geode and Darrel Schneider. Repository: geode Description

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #361 was SUCCESSFUL (with 1410 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #361 was successful (rerun once). --- This build was rerun by John Blum. 1412 tests in total.

Re: Review Request 49666: GEODE-1613 CI failure: ConnectionPoolDUnitTest.test021ClientGetOfInvalidServerEntry

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49666/ --- (Updated July 5, 2016, 11:21 p.m.) Review request for geode, Hitesh Khamesra

Review Request 49666: GEODE-1613 CI failure: ConnectionPoolDUnitTest.test021ClientGetOfInvalidServerEntry

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49666/ --- Review request for geode, Hitesh Khamesra and Udo Kohlmeyer. Bugs: GEODE-1613

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #361 has FAILED (1 tests failed)

--- Spring Data GemFire > Nightly-ApacheGeode > #361 failed. --- Scheduled 1/1412 tests failed. https://build.spring.io/browse/SGF-NAG-361/

[GitHub] incubator-geode pull request #188: GEODE-1598: Fix GfshHistoryJUnitTest

Github user asfgit closed the pull request at: https://github.com/apache/incubator-geode/pull/188 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] incubator-geode pull request #188: GEODE-1598: Fix GfshHistoryJUnitTest

GitHub user gracemeilen opened a pull request: https://github.com/apache/incubator-geode/pull/188 GEODE-1598: Fix GfshHistoryJUnitTest You can merge this pull request into a Git repository by running: $ git pull https://github.com/gracemeilen/incubator-geode develop

Re: Geode website tagged with minor Apache branding issue in audit

+1 We should replace the Apache Geode logo that fades-in when you scroll the page (http://i.imgur.com/XA6SvHb.png) with the feather. (Hope this is what Roman means by "menu bar on the left") On Sat, Jul 2, 2016 at 6:30 AM, Anthony Baker wrote: > ++1 and thanks for the

Re: Build failed in Jenkins: Geode-nightly #520

I filed https://issues.apache.org/jira/browse/GEODE-1620 for the unrecognized options issue. On Tue, Jul 5, 2016 at 10:11 AM, Jinmei Liao wrote: > Let's change the test first and then create a jira ticket to have gfsh fail > on unrecognized options. Thanks! > > On Tue, Jul 5,

Re: Build failed in Jenkins: Geode-nightly #520

Let's change the test first and then create a jira ticket to have gfsh fail on unrecognized options. Thanks! On Tue, Jul 5, 2016 at 9:57 AM, Kirk Lund wrote: > GfshHistoryJUnitTest is now failing after my commit on Friday. > > The test expects unrecognized options to cause the

Re: Build failed in Jenkins: Geode-nightly #520

GfshHistoryJUnitTest is now failing after my commit on Friday. The test expects unrecognized options to cause the command to fail. Replacing our forked version of jopt-simple with a released version has caused us to lose the ability to fail any command that contains unrecognized arguments or

Re: Build failed in Jenkins: Geode-nightly #520

Thanks Jinmei! Can you share with the list the results of your discussion? “If it doesn’t happen on the mailing list, it didn’t happen.” [1] —The Apache Way Anthony [1] https://community.apache.org/newbiefaq.html > On Jul 5, 2016, at 8:50 AM, Jinmei Liao wrote: >

Re: Build failed in Jenkins: Geode-nightly #520

It has something to do with the 7/1 checkin on gfshParser. I'll talk to the team about if they want to revert the changes or fix the test if the change is expected. On Tue, Jul 5, 2016 at 8:28 AM, Jinmei Liao wrote: > I'll take a look. > > On Tue, Jul 5, 2016 at 8:24 AM,

Re: Build failed in Jenkins: Geode-nightly #520

I'll take a look. On Tue, Jul 5, 2016 at 8:24 AM, Anthony Baker wrote: > This test is failing pretty regularly. Any volunteers to take a look? > > Anthony > > On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >

Re: Build failed in Jenkins: Geode-nightly #520

This test is failing pretty regularly. Any volunteers to take a look? Anthony > On Jul 5, 2016, at 7:20 AM, Apache Jenkins Server > wrote: > > geode-core:integrationTest > > com.gemstone.gemfire.management.internal.cli.shell.GfshHistoryJUnitTest > >

Build failed in Jenkins: Geode-nightly #520

See -- [...truncated 537 lines...] :geode-web:javadocJar :geode-web:sourcesJar :geode-web:war :geode-web:signArchives SKIPPED :geode-web-api:jar :geode-web-api:javadoc :geode-web-api:javadocJar