[jira] [Updated] (JDO-696) Throw on unrecognized javax.jdo options
[ https://issues.apache.org/jira/browse/JDO-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-696: - Attachment: JDO-696.src.patch This patch contains fixes only for the api source. Tests will be added when changes for JDO-695 are checked in. Please review for correct list of user-configurable standard properties. > 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] [Updated] (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:all-tabpanel ] Matthew T. Adams updated JDO-684: - Attachment: JDO-684.patch Incorporated changes from conf call feedback on 7 Oct '11. Please review. Once approved, I'll commit & begin release process. > 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] [Updated] (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:all-tabpanel ] Matthew T. Adams updated JDO-684: - Attachment: (was: JDO-684.patch) > 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-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-tabpanel&focusedCommentId=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
[jira] [Updated] (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:all-tabpanel ] Matthew T. Adams updated JDO-694: - Attachment: JDO-694.patch Proposed fix. Sorry about the whitespace. > 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] [Updated] (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:all-tabpanel ] Matthew T. Adams updated JDO-694: - Attachment: (was: JDO-694.patch) > 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] [Updated] (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:all-tabpanel ] Matthew T. Adams updated JDO-694: - Attachment: (was: JDO-694.2.patch) > 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-695) Fix PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Updated] (JDO-695) Fix PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-695: - Attachment: (was: big.patch) > 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] [Updated] (JDO-695) Fix PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-695: - Attachment: JDO-695.patch isolates fixes for this issue > 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] [Updated] (JDO-695) Fix PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-695: - Description: PMFMapMapTest has failing tests, apparently due to classloader issues. (was: This is a rollup task to link to the aforementioned issues & house patches for them.) Summary: Fix PMFMapMapTest (was: Fix for JDO-688 & PMFMapMapTest) > 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: big.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] [Resolved] (JDO-688) javax.jdo.EnhancerTest#testClasspathJar() fails on Windows
[ https://issues.apache.org/jira/browse/JDO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams resolved JDO-688. -- Resolution: Fixed r1180132 | madams | 2011-10-07 13:23:52 -0500 (Fri, 07 Oct 2011) | 1 line JDO-688 > 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] [Updated] (JDO-688) javax.jdo.EnhancerTest#testClasspathJar() fails on Windows
[ https://issues.apache.org/jira/browse/JDO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-688: - Attachment: (was: JDO-688.patch) > 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] [Updated] (JDO-688) javax.jdo.EnhancerTest#testClasspathJar() fails on Windows
[ https://issues.apache.org/jira/browse/JDO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-688: - Attachment: JDO-688.patch isolated fix for this issue > 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] [Updated] (JDO-695) Fix for JDO-688 & PMFMapMapTest
[ https://issues.apache.org/jira/browse/JDO-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-695: - Summary: Fix for JDO-688 & PMFMapMapTest (was: Fix for JDO-693, JDO-688 & PMFMapMapTest) > Fix for 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] [Updated] (JDO-693) Constant string "javax.jdo.option.TransactionType" not defined in javax.jdo.Constants
[ https://issues.apache.org/jira/browse/JDO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-693: - Component/s: (was: specification) Affects Version/s: JDO 3 update 1 > 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 >Affects Versions: JDO 3, JDO 3 update 1 >Reporter: Matthew T. Adams >Assignee: Matthew T. Adams > Fix For: JDO 3 maintenance release 1 > > Attachments: JDO-693.patch > > > 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] [Resolved] (JDO-693) Constant string "javax.jdo.option.TransactionType" not defined in javax.jdo.Constants
[ https://issues.apache.org/jira/browse/JDO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams resolved JDO-693. -- Resolution: Fixed r1180129 | madams | 2011-10-07 13:13:39 -0500 (Fri, 07 Oct 2011) | 1 line > 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 >Affects Versions: JDO 3, JDO 3 update 1 >Reporter: Matthew T. Adams >Assignee: Matthew T. Adams > Fix For: JDO 3 maintenance release 1 > > Attachments: JDO-693.patch > > > 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] [Updated] (JDO-693) Constant string "javax.jdo.option.TransactionType" not defined in javax.jdo.Constants
[ https://issues.apache.org/jira/browse/JDO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew T. Adams updated JDO-693: - Attachment: JDO-693.patch Isolated fix for this issue. > 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 >Affects Versions: JDO 3 >Reporter: Matthew T. Adams >Assignee: Matthew T. Adams > Fix For: JDO 3 maintenance release 1 > > Attachments: JDO-693.patch > > > 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
Minutes: JDO TCK Conference Call Friday, Oct 7, 9 am Pacific Time
Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig Russell Agenda: 1. 3.0.1 patch (see https://issues.apache.org/jira/browse/JDO/fixforversion/12317950) One final bit: the manifest JDO3.MF in the top level directory is used by the tck, which is confusing. It would be nice to see this moved to the tck directory. AI Matthew: move the file to the tck; 3.0.1 will then be ready to go. 2. New JIRAs: https://issues.apache.org/jira/browse/JDO-688 The patch looks good. https://issues.apache.org/jira/browse/JDO-695 This patch was applied and seems to work. Still needs to be reviewed. AI Craig. 3. Other issues https://issues.apache.org/jira/browse/JDO-693 Patch looks good. Action Items from weeks past: [April 8 2011] AI Craig comment on https://issues.apache.org/jira/browse/JDO-617 re the utility of the update operator. [Sep 23 2011] AI Michael prepare spec update for JDOQL changes (JDO-658) and document restrictions on Enum.ordinal and Enum.toString. Create new JIRA for Math methods in JDOQL. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
[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-tabpanel&focusedCommentId=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-693) Constant string "javax.jdo.option.TransactionType" not defined in javax.jdo.Constants
[ https://issues.apache.org/jira/browse/JDO-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122926#comment-13122926 ] Craig L Russell commented on JDO-693: - The patch for TransactionType looks good. > 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 >Affects Versions: JDO 3 >Reporter: Matthew T. Adams >Assignee: Matthew T. Adams > Fix For: JDO 3 maintenance release 1 > > > 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] [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-tabpanel&focusedCommentId=13122925#comment-13122925 ] Michael Bouschen commented on JDO-688: -- The patch lokks good. > 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] [Updated] (JDO-688) javax.jdo.EnhancerTest#testClasspathJar() fails on Windows
[ https://issues.apache.org/jira/browse/JDO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-688: - Affects Version/s: (was: JDO 3 maintenance release 1) JDO 3 Fix Version/s: JDO 3 maintenance release 1 > 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] [Issue Comment Edited] (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-tabpanel&focusedCommentId=13122925#comment-13122925 ] Michael Bouschen edited comment on JDO-688 at 10/7/11 4:18 PM: --- The patch looks good. was (Author: mbo): The patch lokks good. > 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-688) javax.jdo.EnhancerTest#testClasspathJar() fails on Windows
[ https://issues.apache.org/jira/browse/JDO-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122923#comment-13122923 ] Craig L Russell commented on JDO-688: - Looks good. > 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 maintenance release 1 >Reporter: Matthew T. Adams >Assignee: Matthew T. Adams >Priority: Minor > 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-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-tabpanel&focusedCommentId=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
