THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
1) Optional, but recommended - Install git-flow
2) Optional, but recommended - Configure git to cache https credentials. Otherwise you'll need to enter your password every time you push to apache.
3) clone geode repo
git clone https://git-wip-us.apache.org/repos/asf/incubator-geode.git geode cd geode git remote add github https://github.com/apache/incubator-geode git config reviewboard.url https://reviews.apache.org/ git checkout -b develop origin/develop
What this does is create an open directory that is a clone of the apache repository. Any changes you push from here will go directly into the public apache repository.
The 'github' remote is there so you can merge pull requests that other people submit to our project on github. For more info, see the section on accepting pull requests on the apache geode wiki.
The 'maint' remote will be used to keep track of private maintenance branches that are based off of the open source code. There won't be much there until we release 9.0.
The 'github' remote is there so you can merge pull requests that other people submit to our project on github. For more info, see the section on accepting pull requests on the apache geode wiki.
The 'maint' remote will be used to keep track of private maintenance branches that are based off of the open source code. There won't be much there until we release 9.0.
4) initialize git-flow in geode checkout
git flow init
Which branch should be used for bringing forth production releases?- masterBranch name for production releases: [master]Which branch should be used for integration of the "next release"?Branch name for "next release" development: [develop]How to name your supporting branch prefixes?Feature branches? [feature/]Release branches? [release/]Hotfix branches? [hotfix/]Support branches? [support/]Version tag prefix? [] v
5) configure eclipse projects
cd ../closed ./gradlew eclipse
6) build everything
./gradlew build -Dskip.tests=true
7) build everything and run tests
./gradlew build
Now you're ready to follow Developer Workflow.