THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Excerpt | ||
|---|---|---|
| ||
How to report a bug you find in OpenJPA |
| Wiki Markup |
|---|
{scrollbar} |
Found a Bug?
If you think you've found a problem with OpenJPA, there are several ways to proceed.
You can begin by raising the issue on the OpenJPA User or Developer mailing list lists (see Mailing Lists).
You can also search JIRA, our issue-tracking system, to see if the problem has already been noted (visit JIRA). If the issue is not listed there, you can add a new JIRA issue describing it. Please include detailed steps to reproduce the problem.
If you have a fix for the issue, you can generate a patch file to send the fix to us. You need to check out the current source code from Subversion (see Source Code), make the necessary changes (see Coding Standards), and then do a full build with all tests enabled (see Building OpenJPA) and make sure the unit tests runs as expected (try maven -o clean packageinstall to run a full build), and of course, confirm that the problem is actually fixed. Then, go to the trunk root directory of your OpenJPA checkout, and run a command like svn diff > OPENJPA-243<JIRA_NUMBER>-<BRANCH_ID>.patch to generate a patch file.
To submit a patch, create an issue in JIRA that describes the problem, and add your patch file as an attachment (don't forget to select the "Grant license to ASF for inclusion in ASF works" option), and then edit the JIRA to select the Patch Available check box. Please include detailed steps to reproduce the problem in the issue description, and a test case in the patch where possible (see Unit Tests) Testing).
For larger contributions, like new features or more complex bug fixes, you should also have an Individual Contributor License Agreement on file with the ASF.
Thanks for working with us to improve Apache OpenJPA!
Copyright notices for submitted patches
Please see http://www.apache.org/legal/src-headers.html
for details of the following summary.
Apache does not require you to assign ownership or copyright for any patches that you submit via the above process. You retain ownership for all such patches. But Apache does require you to grant Apache a license to use the patch. To do this for new files, do not include a copyright statement in the file but include this license as comments in the header of your source contribution:
Licensed to the Apache Software Foundation (ASF) under one |
or more contributor license agreements. See the NOTICE file |
distributed with this work for additional information |
regarding copyright ownership. The ASF licenses this file |
to you under the Apache License, Version 2.0 (the |
"License"); you may not use this file except in compliance |
with the License. You may obtain a copy of the License at |
http://www.apache.org/licenses/LICENSE-2.0 |
Unless required by applicable law or agreed to in writing, |
software distributed under the License is distributed on an |
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
KIND, either express or implied. See the License for the |
specific language governing permissions and limitations |
under the License. |
Reporting Security Vulnerabilities
The Apache Software Foundation takes a very active stance in eliminating security problems and denial of service attacks against the code we provide.
We strongly encourage folks to report any such problems discovered in OpenJPA to our private PMC mailing list private@openjpa.apache.org first, before disclosing them in a public forum.
Please note that the private PMC mailing list should only be used for reporting undisclosed security vulnerabilities and managing the process of fixing such vulnerabilities until they are made public. We will not accept regular bug reports or other general user queries at this address.
If you need to report a bug that is already a disclosed security vulnerability, please use the regular bug reporting process above.
Questions about:
- how to securely configure OpenJPA
- if a vulnerability applies to your particular application or OpenJPA level
- obtaining further information on a published vulnerability
- availability of patches and/or new releases
should be address to the users mailing list. Please see the Mailing Lists page for details of how to subscribeIf you require that distributions of the project include your copyright notice, you should include with your patch an update to the NOTICE file at trunk/openjpa-project/NOTICE.txt documenting for which files you are notifying your copyright.