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

typos in README

Browse Source
This commit is contained in:
Mark Fisher
2011-08-23 11:17:53 -04:00
parent 90c3bed780
commit 92e59cc0cf
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -12,7 +12,7 @@ repositories that can't be exposed in the poms by default.
SpringSource ToolSuite users (or Eclipse users with the latest
m2eclipse plugin) can import the projects as existing Eclipse
projects. There are plenty of intersteing integration tests (names
projects. There are plenty of interesting integration tests (names
ending with `IntegrationTests`) to show the features of the
framework. Sample applications can be found in the [Spring AMQP
Samples](http://github.com/SpringSource/spring-amqp-samples) project.
@@ -53,7 +53,7 @@ None of these is essential for a pull request, but they will all help. They can
* Use the Spring Framework code format conventions (import `eclipse-code-formatter.xml` from the root of the project if you are using Eclipse).
* Make sure all new .java files to have a simple Javadoc class comment with at least an @author tag identifying you, and preferably at least a paragraph on what the class is for.
* Add the ASF license header comment to all new .java files (copy from existing files in the project)
* Add yourself as an @author to the .java files that you modify substantially (moew than cosmetic changes).
* Add yourself as an @author to the .java files that you modify substantially (more than cosmetic changes).
* Add some Javadocs and, if you change the namespace, some XSD doc elements.
* A few unit tests would help a lot as well - someone has to do it.
* If no-one else is using your branch, please rebase it against the current master (or other target branch in the main project).