THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Post a message to OpenJPA User's list to discuss the issue.
- Search existing issues to see whether someone had already encountered the same issue.
- 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.
- Attach the new test to JIRA issue.
- Check out the Found a Bug page for more details on creating and submitting patches.
I have encountered an issue with OpenJPA and
...
have fixed it in the OpenJPA source 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.
- Create test cases to validate your changes. Here are some useful tips and guidelines on how to develop a test case to contribute to OpenJPA repository.
'svn add'
any new files.- Run
'mvn test -Dtest=<MyTestCase>'
to validate your change. You need to specify the test to run by its simple name without package name. - Run the checkin tests by running
'mvn test'
for any possible regression. This should take around 20-50 minutes or so depending on the release branch.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 - Check out the Found a Bug page for more details on creating and submitting patches.
- Wait for a committer to review and check in your changes.