[jira] [Commented] (JDO-711) Reorganize project sources to abide by maven conventions
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13258353#comment-13258353 ] Matthew T. Adams commented on JDO-711: -- No objections after a month, so I will upload patch for review in prep for commit as part of 3.1. Reorganize project sources to abide by maven conventions Key: JDO-711 URL: https://issues.apache.org/jira/browse/JDO-711 Project: JDO Issue Type: Improvement Components: api, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Priority: Trivial Labels: maven, pom Fix For: JDO 3 maintenance release 1 (3.1) The current source trees for the JDO projects api tck don't abide by maven conventions. This request is to reorganize the source trees so that they do, reducing required pom metadata and enabling new developers to easily comprehend the projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-711) Reorganize project sources to abide by maven conventions
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13231396#comment-13231396 ] Matthew T. Adams commented on JDO-711: -- Anyone object to my doing this for 3.1 since we're going all maven 2 with this release? Reorganize project sources to abide by maven conventions Key: JDO-711 URL: https://issues.apache.org/jira/browse/JDO-711 Project: JDO Issue Type: Improvement Components: api, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Priority: Trivial Labels: maven, pom The current source trees for the JDO projects api tck don't abide by maven conventions. This request is to reorganize the source trees so that they do, reducing required pom metadata and enabling new developers to easily comprehend the projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-710) Edit poms so that the maven eclipse plugin doesn't throw on import
[ https://issues.apache.org/jira/browse/JDO-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13231408#comment-13231408 ] Matthew T. Adams commented on JDO-710: -- Committed: R:\os\jdo\trunksvn ci -m JDO-710, Edit poms so that the maven eclipse plugin doesn't throw on import Sendingapi\pom.xml Adding api\src\main Adding api\src\main\resources Adding api\src\main\resources\META-INF Adding api\src\main\resources\META-INF\NOTICE.txt Sendingtck\pom.xml Adding tck\src\main Adding tck\src\main\resources Adding tck\src\main\resources\META-INF Adding tck\src\main\resources\META-INF\NOTICE.txt Transmitting file data Committed revision 1301658. Edit poms so that the maven eclipse plugin doesn't throw on import -- Key: JDO-710 URL: https://issues.apache.org/jira/browse/JDO-710 Project: JDO Issue Type: Improvement Components: api, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: m2e, maven-eclipse-plugin, pom Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-710.patch Relative paths using .. in poms cause the maven eclipse plugin to throw a NPE. This request is to fix poms so that they don't cause maven eclipse plugin to throw. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-707) Refactor JDO parent child poms
[ https://issues.apache.org/jira/browse/JDO-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13226265#comment-13226265 ] Matthew T. Adams commented on JDO-707: -- The improvement comes when we release the 3.1 artifacts to Maven Central. When I released 3.0.1, I had to manually copy information from the parent pom into the JDO API pom. In 3.1, when we release, we should release not only artifact jdo-api, but also parent-pom. Then, there will not have to be any manual copying from the parent pom into the jdo-api pom. Refactor JDO parent child poms Key: JDO-707 URL: https://issues.apache.org/jira/browse/JDO-707 Project: JDO Issue Type: Improvement Components: api, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: parent, pom Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-707-1.patch Create a parent-pom module, make modules api, exectck tck inherit from it, then create a simple multimodule root pom which can be used to build all projects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-696) Throw on unrecognized javax.jdo options
[ https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13194903#comment-13194903 ] Matthew T. Adams commented on JDO-696: -- Thanks, Andy. I'll have a look fix. Throw on unrecognized javax.jdo options --- Key: JDO-696 URL: https://issues.apache.org/jira/browse/JDO-696 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-696.patch If a user specifies an unrecognized option that begins with JDO's standard prefix javax.jdo., then an exception (JDOUserException or a sub) should be thrown by either the implementation or JDOHelper, depending on the bootstrapping mechanism employed by the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-696) Throw on unrecognized javax.jdo options
[ https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148587#comment-13148587 ] Matthew T. Adams commented on JDO-696: -- I will make the check for known javax.jdo properties case-insensitive so that Javax.JDO is considered to be the same as javax.jdo. Speak up if you no likey. Throw on unrecognized javax.jdo options --- Key: JDO-696 URL: https://issues.apache.org/jira/browse/JDO-696 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: JDO-696.patch If a user specifies an unrecognized option that begins with JDO's standard prefix javax.jdo., then an exception (JDOUserException or a sub) should be thrown by either the implementation or JDOHelper, depending on the bootstrapping mechanism employed by the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148599#comment-13148599 ] Matthew T. Adams commented on JDO-694: -- javax.naming.* should not be optional Automate OSGi bundling in JDO 3.1+ build Key: JDO-694 URL: https://issues.apache.org/jira/browse/JDO-694 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: jdo, osgi Fix For: JDO 3 maintenance release 1 Attachments: JDO-694.patch Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13148639#comment-13148639 ] Matthew T. Adams commented on JDO-694: -- I'll defer to bnd's expertise as to what should be listed in the Import-Package header (bnd is the tool that underlies maven-bundle-plugin). For example, we depend on javax.security, yet bnd does not add an import for that package, but it does add an import for javax.naming. Best Craig I could figure is that bnd knows what should shouldn't be listed in Import-Package. We're going with everything as optional because javax.naming javax.rmi are used only if JNDI is used and the XML APIs are used only if a jdoconfig.xml is parsed. Automate OSGi bundling in JDO 3.1+ build Key: JDO-694 URL: https://issues.apache.org/jira/browse/JDO-694 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: jdo, osgi Fix For: JDO 3 maintenance release 1 Attachments: JDO-694.patch Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-699) Archive unmaintained modules
[ https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145508#comment-13145508 ] Matthew T. Adams commented on JDO-699: -- svn ci -m archiving legacy artifacts Adding archive Adding archive\JDO11.MF Adding archive\JDO20.MF Adding archive\api11 Adding archive\api2 Adding archive\api2-legacy Adding archive\btree Adding archive\enhancer20 Adding archive\fostore20 Adding archive\model20 Adding archive\query20 Adding archive\ri11 Adding archive\runtime20 Adding archive\tck11 Adding archive\tck2 Adding archive\tck2-legacy Adding archive\util20 Deleting trunk\JDO11.MF Deleting trunk\JDO20.MF Deleting trunk\api11 Deleting trunk\api2 Deleting trunk\api2-legacy Deleting trunk\btree Deleting trunk\enhancer20 Deleting trunk\fostore20 Deleting trunk\model20 Deleting trunk\query20 Deleting trunk\ri11 Deleting trunk\runtime20 Deleting trunk\tck11 Deleting trunk\tck2 Deleting trunk\tck2-legacy Deleting trunk\util20 Committed revision 1198735. Archive unmaintained modules Key: JDO-699 URL: https://issues.apache.org/jira/browse/JDO-699 Project: JDO Issue Type: Improvement Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, model2, query2, ri11, runtime2, tck11, tck2-legacy, util2 Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 There are many modules in the trunk of the JDO source repo that are no longer maintained. I propose to create a new directory archive as a peer to trunk, branches, releases, and site, then svn-move them from trunk to archive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-699) Archive unmaintained modules
[ https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13138558#comment-13138558 ] Matthew T. Adams commented on JDO-699: -- WDYT, everyone? Archive unmaintained modules Key: JDO-699 URL: https://issues.apache.org/jira/browse/JDO-699 Project: JDO Issue Type: Improvement Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, model2, query2, ri11, runtime2, tck11, tck2-legacy, util2 Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 There are many modules in the trunk of the JDO source repo that are no longer maintained. I propose to create a new directory archive as a peer to trunk, branches, releases, and site, then svn-move them from trunk to archive. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-699) Archive unmaintained modules
[ https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13128204#comment-13128204 ] Matthew T. Adams commented on JDO-699: -- A simpler alternative is to just delete the unused projects. They are present in the branches, anyway. I'll edit this issue accordingly. Archive unmaintained modules Key: JDO-699 URL: https://issues.apache.org/jira/browse/JDO-699 Project: JDO Issue Type: Improvement Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, model2, query2, ri11, runtime2, tck11, tck2-legacy, util2 Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 There are many modules in the trunk of the JDO source repo that are no longer maintained. I propose moving these to an archive folder that's a peer to trunk branches. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-699) Delete unmaintained modules
[ https://issues.apache.org/jira/browse/JDO-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13128241#comment-13128241 ] Matthew T. Adams commented on JDO-699: -- I won't attach the patch for this (38 Mb uncompressed, 3 Mb zipped), only commit when we approve. Delete unmaintained modules --- Key: JDO-699 URL: https://issues.apache.org/jira/browse/JDO-699 Project: JDO Issue Type: Improvement Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, model2, query2, ri11, runtime2, tck11, tck2-legacy, util2 Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 There are many modules in the trunk of the JDO source repo that are no longer maintained. I propose to delete them from trunk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-696) Throw on unrecognized javax.jdo options
[ https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13127700#comment-13127700 ] Matthew T. Adams commented on JDO-696: -- Feeback from conf call: * minor patch changes (forthcoming) * add tests to api project * add TCK tests for IUT * spec updates Throw on unrecognized javax.jdo options --- Key: JDO-696 URL: https://issues.apache.org/jira/browse/JDO-696 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: JDO-696.src.patch If a user specifies an unrecognized option that begins with JDO's standard prefix javax.jdo., then an exception (JDOUserException or a sub) should be thrown by either the implementation or JDOHelper, depending on the bootstrapping mechanism employed by the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-688) javax.jdo.EnhancerTest#testClasspathJar() fails on Windows
[ https://issues.apache.org/jira/browse/JDO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13124113#comment-13124113 ] Matthew T. Adams commented on JDO-688: -- Andy noticed a compilation error in trunk\api, which made me realize that I missed a bunch of files when attempting to isolate changes for this issue. Trunk has been updated with those changes. javax.jdo.EnhancerTest#testClasspathJar() fails on Windows -- Key: JDO-688 URL: https://issues.apache.org/jira/browse/JDO-688 Project: JDO Issue Type: Bug Components: tck Affects Versions: JDO 3 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Priority: Minor Fix For: JDO 3 maintenance release 1 Attachments: JDO-688.patch javax.jdo.EnhancerTest#testClasspathJar() fails because the executable rm is not available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-695) Fix PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13124121#comment-13124121 ] Matthew T. Adams commented on JDO-695: -- Changes for this patch were checked in on 10 Oct due to errors while trying to isolate changes for JDO-688. Fix PMFMapMapTest - Key: JDO-695 URL: https://issues.apache.org/jira/browse/JDO-695 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: JDO-695.patch PMFMapMapTest has failing tests, apparently due to classloader issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
[
https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13122853#comment-13122853
]
Matthew T. Adams commented on JDO-684:
--
@Craig, I take you meant that it also updates api/../JDO3.MF. I included a
change to that file for completeness.
It's used in tck/project.properties, line 21: maven.jar.manifest =
${basedir}/../JDO3.MF
Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
--
Key: JDO-684
URL: https://issues.apache.org/jira/browse/JDO-684
Project: JDO
Issue Type: Bug
Components: api
Affects Versions: JDO 3
Reporter: Matthew T. Adams
Assignee: Matthew T. Adams
Labels: export-package, jdo, osgi
Fix For: JDO 3 update 1
Attachments: JDO-684.patch
The manifest for the JDO API project fails to specify package versions in its
OSGi Export-Package entry. I've added these revised the version from 3.0
to 3.0.1, as the 3.0 artifacts have already been published. Without the
package-level version specifications, Virgo (Eclipse Equinox + Spring dm
Server additions) reports version 0.0.0 for all packages, causing missing
bundle dependencies downstream, including DataNucleus.
Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-695) Fix for JDO-693, JDO-688 PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13122929#comment-13122929 ] Matthew T. Adams commented on JDO-695: -- I will: * separate patches for JDO-693 JDO-688 and commit those changes * remove the incorporation of those patches in this issue * upload a new patch with just changes for PMFMapMapTest Fix for JDO-693, JDO-688 PMFMapMapTest Key: JDO-695 URL: https://issues.apache.org/jira/browse/JDO-695 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: big.patch This is a rollup task to link to the aforementioned issues house patches for them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-695) Fix PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13123047#comment-13123047 ] Matthew T. Adams commented on JDO-695: -- The tasks in my comment dated 07/Oct/11 16:26 are done. Please review patch. Upon successful review, I'll commit. Fix PMFMapMapTest - Key: JDO-695 URL: https://issues.apache.org/jira/browse/JDO-695 Project: JDO Issue Type: Task Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Attachments: JDO-695.patch PMFMapMapTest has failing tests, apparently due to classloader issues. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13123053#comment-13123053 ] Matthew T. Adams commented on JDO-694: -- Please review patch. Upon successful review, I'll commit. Automate OSGi bundling in JDO 3.1+ build Key: JDO-694 URL: https://issues.apache.org/jira/browse/JDO-694 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2 Reporter: Matthew T. Adams Assignee: Matthew T. Adams Labels: jdo, osgi Fix For: JDO 3 maintenance release 1 Attachments: JDO-694.patch Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
