THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Excerpt | ||
|---|---|---|
| ||
Information on getting involved with the OpenJPA project |
Join the Apache OpenJPA Community
The Apache OpenJPA project is being built by the open source community for the open source community - we welcome your input and contributions!
What we are looking for
- Source code and fixes contributions
- Test cases for issues encountered during application development
- Documentation assistance
- Product and feature suggestions
- Detailed and constructive feedback
- Articles and whitepapers
How do I Contribute?
- To discuss Apache OpenJPA topics check out the mailing lists.
- Bugs and other issues can be posted on the project JIRA.
I have encountered an issue with OpenJPA. What do I now?
- Post a message to OpenJPA User's list to discuss the issue
- Search existing issues to see whether someone had encountered the same issue before
- If this issue is never encountered before, create a JIRA issue.
- Develop a test case to demonstrate the issue. Here are some useful tips and guidelines on how to develop a test case to contribute to OpenJPA repository.
I've written some code; how do I get the changes into OpenJPA?
- Create a JIRA issue that describes the changes you've made (you'll need an Apache JIRA account to do this).
- Check out the OpenJPA source code and make your changes. Don't forget to create test cases for your changes.
- 'svn add' any new files.
- Run the checkin tests by running 'mvn test'. This should take around 20 minutes or so.
- Attach the output of 'svn diff' to the newly-created JIRA. The name of the patch file should be in the format "OPENJPA-<JIRA_NUMBER>.patch". Don't forget to assign copyright to the ASF.
- Wait for a committer to review and check in your changes.