[jira] [Created] (JDO-714) Move version control to git
Move version control to git --- Key: JDO-714 URL: https://issues.apache.org/jira/browse/JDO-714 Project: JDO Issue Type: Improvement Components: site and infrastructure Reporter: Matthew T. Adams Priority: Minor Distributed version control systems have some nice productivity community participation features, and is gaining in popularity. I propose we switch from svn to git. -- 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] [Created] (JDO-710) Edit poms so that the maven eclipse plugin doesn't throw on import
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 Fix For: JDO 3 maintenance release 1 (3.1) 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] [Created] (JDO-711) Reorganize project sources to abide by maven conventions
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 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] [Created] (JDO-709) Standardize field/property converters
Standardize field/property converters - Key: JDO-709 URL: https://issues.apache.org/jira/browse/JDO-709 Project: JDO Issue Type: New Feature Components: api Reporter: Matthew T. Adams Assignee: Matthew T. Adams Priority: Minor Fix For: JDO 3 maintenance release 2 (3.2) This request is to standardize a user's ability to specify conversions of fields or properties of persistence-capable classes. Currently, this is left to vendor extensions. -- 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] [Created] (JDO-707) Refactor JDO parent child poms
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 Fix For: JDO 3 maintenance release 1 (3.1) 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] [Created] (JDO-708) Create JIRA component entry for exectck parent-pom modules
Create JIRA component entry for exectck parent-pom modules -- Key: JDO-708 URL: https://issues.apache.org/jira/browse/JDO-708 Project: JDO Issue Type: Task Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 (3.1) The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too. -- 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] [Created] (JDO-703) Support datastore multitenancy
Support datastore multitenancy -- Key: JDO-703 URL: https://issues.apache.org/jira/browse/JDO-703 Project: JDO Issue Type: New Feature Components: api, tck Affects Versions: JDO 3 maintenance release 2 (3.2) Reporter: Matthew T. Adams Support database multitenancy as an optional feature (using standard JDO option javax.jdo.option.Multitenancy), where different customers' data can be stored in the same database and the implementation amends all query filters to include a tenant identifier where instructed by the user via metadata. I forsee a minimal need for only two pieces of metadata information: first, that where multitenancy should be used, and second, the multitenancy mapping information. Multitenancy could be given by the developer at the PMF or PM level, where he specifies a property, say javax.jdo.multitenancy.discriminator or similar, corresponding to new PMF or PM property multitenantDiscriminator, whose value represents the tenant discriminator. Then, queries, loads via id, or dereferences including any entities identified via metadata as multitenant would automatically include in the underlying datastore query filter a condition that uses the tenant discriminator to include only those entities that have the given tenant discriminator. The entire persistence unit (PMF), persistence context (PM), individual packages, or individual classes could be identified as multitenant via metadata (a @Multitenant annotation or external metadata). Similarly, discriminator mapping information could be defaulted or supplied in a manner similar to existing mapping metadata. -- 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] [Created] (JDO-698) Add TCK tests for JDO-696
Add TCK tests for JDO-696 - Key: JDO-698 URL: https://issues.apache.org/jira/browse/JDO-698 Project: JDO Issue Type: Test Components: tck Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Fix For: JDO 3 maintenance release 1 Write TCK tests for JDO-696. This involves passing properties directly into the IUT's implementation-specific PMF constructor a Map of properties containing properties beginning with javax.jdo. but that are unknown. -- 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] [Created] (JDO-699) Archive unmaintained modules
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] [Created] (JDO-700) exectck plugin throws StringIndexOutOfBoundsException
exectck plugin throws StringIndexOutOfBoundsException
-
Key: JDO-700
URL: https://issues.apache.org/jira/browse/JDO-700
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1
Reporter: Matthew T. Adams
Steps to reproduce:
1. Get latest trunk from svn.
2. Build api exectck modules.
3. Issue mvn clean install command in the tck project
Output is below:
...[snip]...
* Installation of schema8.sql for derby datastoreidentity is complete. See
diagnostic output in C:\temp\jdo\trunk\tck\target\logs\database.
* Installing schema11.sql for derby datastoreidentity
* Installation of schema11.sql for derby datastoreidentity is complete. See
diagnostic output in C:\temp\jdo\trunk\tck\target\logs\database.
[INFO] [jdo-exectck:enhance {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] String index out of range: -1
[INFO]
[INFO] Trace
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1931)
at java.lang.String.substring(String.java:1904)
at org.apache.jdo.exectck.Enhance.execute(Enhance.java:178)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 1 minute 43 seconds
[INFO] Finished at: Sat Oct 15 11:34:29 CDT 2011
[INFO] Final Memory: 48M/738M
[INFO]
'cmd' is not recognized as an internal or external command,
operable program or batch file.
--
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] [Created] (JDO-689) JDO 3.0 specification refers to property javax.jdo.spi.PropertiesResourceName but javax.jdo.Constants calls it javax.jdo.spi.ResourceName
JDO 3.0 specification refers to property javax.jdo.spi.PropertiesResourceName but javax.jdo.Constants calls it javax.jdo.spi.ResourceName - Key: JDO-689 URL: https://issues.apache.org/jira/browse/JDO-689 Project: JDO Issue Type: Bug Components: api, specification Affects Versions: JDO 3, JDO 2 maintenance release 2, JDO 2 maintenance release 1 update 1, JDO 2 maintenance release 1, JDO 2 maintenance release 2 update 1, JDO 3 update 1, JDO 3 maintenance release 1, JDO 3 maintenance release 2 Reporter: Matthew T. Adams Section 11.1.1 Construction by Properties, page 103, paragraph 6, bullet point 2 says 'the Properties instance passed to the static method will contain a property with a key of javax.jdo.spi.PropertiesResourceName, and a value equal to the name of the resource'. The string constant in the JDO API code doesn't exist. javax.jdo.Constants contains the following member: static String PROPERTY_SPI_RESOURCE_NAME = javax.jdo.option.spi.ResourceName; I suggest updating the spec to reflect the correct string in the code rather than modifying the code. I discovered this in JDO 3.1, but may effect versions of the specification beginning with 2.1 and later as the javadoc for this constant includes @since 2.1. -- 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] [Created] (JDO-690) Constant string javax.jdo.Name not defined in javax.jdo.Constants
Constant string javax.jdo.Name not defined in javax.jdo.Constants --- Key: JDO-690 URL: https://issues.apache.org/jira/browse/JDO-690 Project: JDO Issue Type: Bug Components: api, specification Affects Versions: JDO 3 Reporter: Matthew T. Adams The JDO 3.0 specification, page 103, bullet point 3 says 'the Properties instance passed to the static method will contain a property with a key of javax.jdo.Name, and a value equal to the name of the persistence manager factory in the jdoconfig.xml file.' There is no such string constant defined in javax.jdo.Constants. I'm wondering if the specification should say javax.jdo.option.Name here, as that constant is defined in javax.jdo.Constants. This bug is similar to JDO-689. -- 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] [Created] (JDO-691) Typo in heading 11.1.4
Typo in heading 11.1.4 -- Key: JDO-691 URL: https://issues.apache.org/jira/browse/JDO-691 Project: JDO Issue Type: Bug Components: specification Reporter: Matthew T. Adams Priority: Trivial Heading 11.1.4 reads jdoconfg.xml should read jdoconfig.xml. -- 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] [Created] (JDO-692) Constant string javax.jdo.spi.PropertiesFileName not defined in javax.jdo.Constants
Constant string javax.jdo.spi.PropertiesFileName not defined in javax.jdo.Constants - Key: JDO-692 URL: https://issues.apache.org/jira/browse/JDO-692 Project: JDO Issue Type: Bug Components: api, specification Affects Versions: JDO 3 Reporter: Matthew T. Adams The JDO 3.0 specification page 103, bullet point 1 says 'the Map instance passed to the static method will contain a property with a key of javax.jdo.spi.PropertiesFileName, and a value equal to the result of calling getAbsolutePath() on the file parameter'. There is no such constant defined in javax.jdo.Constants. -- 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] [Created] (JDO-693) Constant string javax.jdo.option.TransactionType not defined in javax.jdo.Constants
Constant string javax.jdo.option.TransactionType not defined in javax.jdo.Constants - Key: JDO-693 URL: https://issues.apache.org/jira/browse/JDO-693 Project: JDO Issue Type: Bug Components: api, specification Reporter: Matthew T. Adams The JDO 3.0 specification page 102, 7th bullet point from the bottom of the page refers to property javax.jdo.option.TransactionType but there is no such constant in javax.jdo.Constants. -- 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] [Created] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
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 Fix For: JDO 3 maintenance release 1 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
