Spring/spring-data-geode
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixed up the Spring Data GemFire GitHub project page, correcting links, updating Spring Maven Repo URLs to repo.spring.io, switching references from the Spring Forum to StackOverflow and so on.

Browse Source
This commit is contained in:
John Blum
2014-09-02 16:30:09 -07:00
parent 5a1b8caf28
commit db4b122d82
1 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
README.md
View File

@@ -1,8 +1,8 @@
Spring Data GemFire
===================
The primary goal of the [Spring Data GemFire](http://www.springsource.org/spring-gemfire) project is to make it easier to build highly scalable Spring-powered applications using
[Pivotal GemFire](http://www.gopivotal.com/big-data/pivotal-gemfire#details) as a distributed [data management](http://www.springsource.com/products/data-management) platform.
The primary goal of the [Spring Data GemFire](http://http://projects.spring.io/spring-data-gemfire) project is to make it easier to build highly scalable, Spring-powered applications using
[Pivotal GemFire](http://www.pivotal.io/big-data/pivotal-gemfire) as a distributed, data management platform.
# Examples
@@ -10,10 +10,10 @@ For examples on using the Spring Data GemFire, see the [spring-gemfire-examples]
# Getting Help
Read the main project [website](http://www.springsource.org/spring-gemfire) and the [User Guide](http://static.springsource.org/spring-gemfire/docs/current/reference/html/).
Look at the source code and the [JavaDocs](http://static.springsource.org/spring-gemfire/docs/current/api/).
For more detailed questions, use the [forum](http://forum.springsource.org/forumdisplay.php?f=80).
If you are new to Spring as well as to Spring Data GemFire, look for information about [Spring projects](http://www.springsource.org/projects).
Read the main project [website](http://projects.spring.io/spring-data-gemfire/) and the [User Guide](http://docs.spring.io/spring-data-gemfire/docs/current/reference/html/).
Look at the source code and the [JavaDocs](http://docs.spring.io/spring-data-gemfire/docs/current/api/).
For more detailed questions, visit [StackOverflow](https://stackoverflow.com/questions/tagged/spring-data-gemfire).
If you are new to Spring as well as to Spring Data GemFire, look for information about [Spring projects](http://spring.io/projects).
Quick Start
-----------
@@ -36,21 +36,21 @@ For those in a hurry:
<id>spring-maven-snapshot</id>
<snapshots><enabled>true</enabled></snapshots>
<name>Springframework Maven SNAPSHOT Repository</name>
<url>http://repo.springsource.org/snapshot</url>
<url>http://repo.spring.io/snapshot</url>
</repository>
<!-- used for milestone/rc releases -->
<repository>
<id>spring-maven-milestone</id>
<name>Springframework Maven Milestone Repository</name>
<url>http://repo.springsource.org/milestone</url>
<url>http://repo.spring.io/milestone</url>
</repository>
<!-- required for gemfire jar -->
<repository>
<id>spring-maven-plugins-release</id>
<name>Springframework Maven Plugins Release Repository</name>
<url>http://repo.springsource.org/plugins-release</url>
<url>http://repo.spring.io/plugins-release</url>
</repository>
~~~~~
@@ -58,9 +58,9 @@ For those in a hurry:
~~~~~ groovy
repositories {
mavenRepo name: "spring-snapshot", urls: "http://repo.springsource.org/snapshot"
mavenRepo name: "spring-milestone", urls: "http://repo.springsource.org/milestone"
mavenRepo name: "spring-plugins" , urls: "http://repo.springsource.org/plugins-release"
mavenRepo name: "spring-snapshot", urls: "http://repo.spring.io/snapshot"
mavenRepo name: "spring-milestone", urls: "http://repo.spring.io/milestone"
mavenRepo name: "spring-plugins" , urls: "http://repo.spring.io/plugins-release"
}
dependencies {
@@ -68,7 +68,7 @@ dependencies {
}
~~~~~
Latest GA release is _1.4.0.RELEASE_
Latest GA release is _1.4.4.RELEASE_
Latest nightly build is _1.5.0.BUILD-SNAPSHOT_
@@ -123,9 +123,9 @@ depending on your editor.
Here are some ways for you to get involved in the community:
* Get involved with the Spring community on the Spring Community Forums. Please help out on the [forum](http://forum.springsource.org/forumdisplay.php?f=80) by responding to questions and joining the debate.
* Create [JIRA](https://jira.springframework.org/browse/SGF) tickets for bugs and new features and comment and vote on the ones that you are interested in.
* Github is for social coding: if you want to write code, we encourage contributions through pull requests from [forks of this repository](http://help.github.com/forking/). If you want to contribute code this way, please reference a JIRA ticket as well covering the specific issue you are addressing.
* Watch for upcoming articles on Spring by [subscribing](http://www.springsource.org/node/feed) to springframework.org
* Get involved with the Spring community on the Spring Community Forums (now on StackOverflow). Please help out on the [forum](https://stackoverflow.com/questions/tagged/spring-data-gemfire) by responding to questions and joining the debate.
* Create [JIRA](https://jira.spring.io/browse/SGF) tickets for bugs and new features and comment and vote on the ones that you are interested in.
* GitHub is for social coding. If you want to write code, we encourage contributions through pull requests from [forks of this repository](http://help.github.com/forking/). If you want to contribute code this way, please reference a JIRA ticket as well covering the specific issue you are addressing.
* Watch for upcoming articles on Spring by [subscribing](http://assets.spring.io/drupal/node/feed.xml) to springframework.org
Before we accept a non-trivial patch or pull request we will need you to sign the [contributor's agreement](https://support.springsource.com/spring_committer_signup). Signing the contributor's agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.