[jira] [Resolved] (JDO-716) Convert spec to OpenOffice
[ https://issues.apache.org/jira/browse/JDO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse resolved JDO-716. - Resolution: Fixed Fix Version/s: JDO 3 maintenance release 1 (3.1) Done! Convert spec to OpenOffice -- Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse Assignee: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: OOO.jar To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JDO-716) Convert spec to OpenOffice
[ https://issues.apache.org/jira/browse/JDO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse closed JDO-716. --- Convert spec to OpenOffice -- Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse Assignee: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: OOO.jar To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Release not on mirrors
Hi, I've updated the web site with a new download page for the 3.1-rc1 release, but the release does not appear to be on the mirrors, for example http://mirrors.ibiblio.org/apache/db/jdo/. The links that I used are also wrong, but there's no sense fixing that until the release is actually available. -- Michelle
Re: Release not on mirrors
Yes, and we could just have hard-coded links on the downloads page that point there. At least as a temporary fix, I will do that -- thanks for the idea. However, we and other Apache projects have always used a CGI script that links to a randomly selected mirror and that now does not work. -- Michelle Andy Jefferson a...@datanucleus.org wrote: I've updated the web site with a new download page for the 3.1-rc1 release, but the release does not appear to be on the mirrors, for example http://mirrors.ibiblio.org/apache/db/jdo/. The links that I used are also wrong, but there's no sense fixing that until the release is actually available. Maven repos are not IBiblio now AFAIK. More like http://central.maven.org/maven2/javax/jdo/jdo-api/ and 3.1-rc1 is present. -- Andy DataNucleus (Web: http://www.datanucleus.org Twitter: @datanucleus)
Minutes: JDO TCK Conference Call Friday October 25, 9 am Pacific Time
Attendees: Michael Bouschen, Michelle Caisse Note: For next week's meeting Daylight Savings Time is ended in the U.S., but not in Europe. The meeting will be one hour earlier in regions that are still observing Daylight Savings Time. 1. JDO release JDO 3.1-rc1: JDO web site updates Web site still needs to be updated. 2. JDO specification update Index cross-reference type has been fixed and pdf updated. Action item: Please to svn update and review the spec pdf (trunk/specification/OOO/JDO_3_1-rc1.pdf). 3. Other issues We still need to merge changes from the 3.1-rc1 branch to the trunk. Action Items from weeks past: [May 10 2013] AI Everyone take a look Apache ISIS and maybe subscribe to ISIS mail lists. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
[RESULT][VOTE] JDO 3.1-rc1 release
JDO 3.1-rc1 has been approved as an official Apache JDO release. Thanks to all who worked on the release and who voted. +1 Matthew Adams Michael Bouschen (pmc) Michelle Caisse (pmc) Craig Russell (pmc) Gordan Vosicki There were no other votes. -- Michelle
Re: [VOTE] Please vote on JDO 3.1-rc1 release
+1 -- Michelle On 9/29/2013 10:41 AM, Michelle Caisse wrote: All, Please vote on the JDO 3.1-rc1 release. Voting will be open until Thursday, October 3. You may download the JDO 3.1-rc1 release artifacts from the staging repository: https://repository.apache.org/content/repositories/orgapachejdo-088/ The TCK release artifacts are jdo-3.1-rc1-src.tar.gz and jdo-3.1-rc1-src.zip in https://repository.apache.org/content/repositories/orgapachejdo-088/org/apache/jdo/3.1-rc1/. The JDO api release artifacts are jdo-3.1-rc1.jar, jdo-3.1-rc1-javadoc.jar and jdo-3.1-rc1-sources.jar. -- Michelle
[VOTE] Please vote on JDO 3.1-rc1 release
All, Please vote on the JDO 3.1-rc1 release. Voting will be open until Thursday, October 3. You may download the JDO 3.1-rc1 release artifacts from the staging repository: https://repository.apache.org/content/repositories/orgapachejdo-088/ The TCK release artifacts are jdo-3.1-rc1-src.tar.gz and jdo-3.1-rc1-src.zip in https://repository.apache.org/content/repositories/orgapachejdo-088/org/apache/jdo/3.1-rc1/. The JDO api release artifacts are jdo-3.1-rc1.jar, jdo-3.1-rc1-javadoc.jar and jdo-3.1-rc1-sources.jar. -- Michelle
JDO TCK Conference Call Friday Septembe1 20, 9 am Pacific Time
Hi, We will have our regular meeting Friday, September 20 at 9 am PacificTime (PT) to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. JDO release candidate https://issues.apache.org/jira/browse/JDO-723 - Closing a sonatype repository. 4. Other issues Action Items from weeks past: [May 10 2013] AI Everyone take a look Apache ISIS and maybe subscribe to ISIS mail lists. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
Please test staged JDO 3.1-rc1 release
Please download the JDO 3.1-rc1 release artifacts from the staging repository: https://repository.apache.org/content/repositories/orgapachejdo-023/ If you find any issues, please report them to this list jdo-dev@db.apache.org -- Michelle
JDO TCK Conference Call Friday September 13, 9 am Pacific Daylight Time
Hi, We will have our regular meeting Friday, September 13 at 9 am Pacific Daylight Time (PDT) to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. JDO release candidate https://issues.apache.org/jira/browse/JDO-723 - Closing a sonatype repository. 4. Other issues Action Items from weeks past: [May 10 2013] AI Everyone take a look Apache ISIS and maybe subscribe to ISIS mail lists. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
Stuck on Nexus
I am attempting to close a staged repository in Nexus/Sonatype. https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository I'm not finding a repository for JDO. We followed the instructions to enable Nexus access: https://issues.apache.org/jira/browse/INFRA-6481 No clue what to do now. -- Michelle
[jira] [Commented] (JDO-723) Update release process for 3.1
[ https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13761162#comment-13761162 ] Michelle Caisse commented on JDO-723: - Per Matthew's suggestion, this appears to be an issue with the maven release plugin and cygwin. Executing the command from a Windows command window works. Update release process for 3.1 -- Key: JDO-723 URL: https://issues.apache.org/jira/browse/JDO-723 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: apache-release.patch, release.properties The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure for testing and distributing releases has changed. We need to update our infrastructure, process, and documents to reflect the new situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-723) Update release process for 3.1
[ https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756231#comment-13756231 ] Michelle Caisse commented on JDO-723: - On re-executing mvn release:prepare -Papache-release, I get this build failure: [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] [INFO] [INFO] Total time: 42 minutes 42 seconds [INFO] [INFO] Finished at: Mon Sep 02 12:37:30 MST 2013 [INFO] [INFO] Final Memory: 124M/542M [INFO] [INFO] [INFO] Checking in modified POMs... [INFO] Executing: cmd.exe /X /C svn --non-interactive commit --file C:\cygwin\tmp\maven-scm-1895016991.commit --targets C:\cygwin\tmp\maven-scm-407612330323657141-targets [INFO] Working directory: C:\jdo\branches\3.1-rc1 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: E155010: Commit failed (details follow): svn: E155010: The node '/cygdrive/c/jdo/branches/3.1-rc1/C:/jdo/branches' was not found. Update release process for 3.1 -- Key: JDO-723 URL: https://issues.apache.org/jira/browse/JDO-723 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: apache-release.patch The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure for testing and distributing releases has changed. We need to update our infrastructure, process, and documents to reflect the new situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-723) Update release process for 3.1
[ https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756230#comment-13756230 ] Michelle Caisse commented on JDO-723: - Work-around: After running mvn release:prepare -Papache-release, which updates the version number in pom.xml to the release version, manually install api and exec-tck by changing to those directories, respectively, and doing mvn install. Update release process for 3.1 -- Key: JDO-723 URL: https://issues.apache.org/jira/browse/JDO-723 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: apache-release.patch The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure for testing and distributing releases has changed. We need to update our infrastructure, process, and documents to reflect the new situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-723) Update release process for 3.1
[
https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755873#comment-13755873
]
Michelle Caisse commented on JDO-723:
-
Note for future reference: On mvn release:prepare -Papache-release, I get the
following:
INFO]
[INFO] [INFO] [jar:jar {execution: default-jar}]
[INFO] [INFO] Building jar:
C:\jdo\branches\3.1-rc1\tck\target\jdo-tck-3.1-rc1.jar
[INFO] [INFO] [assembly:single {execution: source-release-assembly}]
[INFO] [INFO] Skipping the assembly in this project because it's not the
Execution Root
[INFO] [INFO] Preparing source:jar
[INFO] Downloading:
http://repo1.maven.org/maven2/org/apache/jdo/jdo-exectck/3.1-rc1/jdo-exectck-3.1-rc1.jar
[INFO] [INFO] Unable to find resource
'org.apache.jdo:jdo-exectck:maven-plugin:3.1-rc1' in repository central
(http://repo1.maven.org/maven2)
[INFO] [INFO]
[INFO] [ERROR] BUILD FAILURE
[INFO] [INFO]
[INFO] [INFO] A required plugin was not found: Plugin could not be found -
check that the goal name is correct: Unable to download the artifact from any
repository
[INFO]
[INFO] Try downloading the file manually from the project website.
[INFO]
[INFO] Then, install it using the command:
[INFO] mvn install:install-file -DgroupId=org.apache.jdo
-DartifactId=jdo-exectck -Dversion=3.1-rc1 -Dpackaging=maven-plugin
-Dfile=/path/to/file
[INFO]
[INFO] Alternatively, if you host your own repository you can deploy the file
there:
[INFO] mvn deploy:deploy-file -DgroupId=org.apache.jdo
-DartifactId=jdo-exectck -Dversion=3.1-rc1 -Dpackaging=maven-plugin
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[INFO]
[INFO]
[INFO] org.apache.jdo:jdo-exectck:maven-plugin:3.1-rc1
[INFO]
[INFO] from the specified remote repositories:
[INFO] central (http://repo1.maven.org/maven2)
[INFO]
[INFO]
[INFO] org.apache.jdo:jdo-exectck:maven-plugin:3.1-rc1
[INFO]
[INFO] from the specified remote repositories:
[INFO] central (http://repo1.maven.org/maven2)
Update release process for 3.1
--
Key: JDO-723
URL: https://issues.apache.org/jira/browse/JDO-723
Project: JDO
Issue Type: Task
Components: site and infrastructure
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: apache-release.patch
The 3.1 release is the first JDO release using maven 2. In addition the
Apache infrastructure for testing and distributing releases has changed. We
need to update our infrastructure, process, and documents to reflect the new
situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-723) Update release process for 3.1
[ https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13755876#comment-13755876 ] Michelle Caisse commented on JDO-723: - It looks like we have a problem with the dependency on the exec-tck plugin, which is part of the project. Do we have to release the plug-in separately, then release the other artifacts? Update release process for 3.1 -- Key: JDO-723 URL: https://issues.apache.org/jira/browse/JDO-723 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: apache-release.patch The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure for testing and distributing releases has changed. We need to update our infrastructure, process, and documents to reflect the new situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
JDO 3.1 SNAPSHOT deployed
All, Please review the artifacts deployed to https://repository.apache.org/content/repositories/snapshots/org/apache/. What you see is what you get with the current version of jdo/branches/3.1-rc1, following the release process documented in jdo/HowToReleaseJDO.html through step 10. -- Michelle
Re: Internal dependency problem with clean build on the release branch
://stackoverflow.com/questions/8411424/automating-maven-artifact-releasing Michael has some familiarity with the maven versions plugin that is mentioned in the response. -- Michelle On 8/10/2013 12:26 PM, Craig L Russell wrote: Sounds pretty strange. So it would be impossible to release co-dependent artifacts? Craig On Aug 10, 2013, at 11:03 AM, Michelle Caisse wrote: Hi all, Preparatory to attempting a release, I cleaned my local repository and did mvn clean install. On building exectck, I got a build error: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) javax.jdo:jdo-api:jar:3.1 This is because, per the apache instructions, our release artifacts have -SNAPSHOT versions, but all dependencies, including the dependency on the api jar that we are in the process of releasing, are to non -SNAPSHOT versions. So, we build jdo-api-3.1-SNAPSHOT.jar, but we are dependent on jdo-api-3.1.jar. What is the best way around this issue? -- Michelle 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!
JNDI download
Our documentation's link to the JNDI download page now takes you to a generic Java download page: http://java.sun.com/products/jndi/downloads/index.html Is there a new location for downloading the JNDI files? -- Michelle
Re: JNDI download
Thanks. -- Michelle On 8/15/2013 3:07 PM, Craig L Russell wrote: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-java-plat-419418.html#7110-jndi-1.2.1-oth-JPR comes from http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-java-plat-419418.html comes from http://www.google.com/search?client=safarirls=enq=download+jndi+file+system+providerie=UTF-8oe=UTF-8 Maybe we should point to one of these? Craig On Aug 15, 2013, at 2:51 PM, Michelle Caisse wrote: Our documentation's link to the JNDI download page now takes you to a generic Java download page: http://java.sun.com/products/jndi/downloads/index.html Is there a new location for downloading the JNDI files? -- Michelle 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!
Internal dependency problem with clean build on the release branch
Hi all, Preparatory to attempting a release, I cleaned my local repository and did mvn clean install. On building exectck, I got a build error: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) javax.jdo:jdo-api:jar:3.1 This is because, per the apache instructions, our release artifacts have -SNAPSHOT versions, but all dependencies, including the dependency on the api jar that we are in the process of releasing, are to non -SNAPSHOT versions. So, we build jdo-api-3.1-SNAPSHOT.jar, but we are dependent on jdo-api-3.1.jar. What is the best way around this issue? -- Michelle
Re: Internal dependency problem with clean build on the release branch
Yeah, I don't know of a way unless there's some kind of option in the maven release plugin that lets you set up your pom some other way. Here's a link to someone who seems to have a similar problem, as far as I understand what they are saying: http://stackoverflow.com/questions/8411424/automating-maven-artifact-releasing Michael has some familiarity with the maven versions plugin that is mentioned in the response. -- Michelle On 8/10/2013 12:26 PM, Craig L Russell wrote: Sounds pretty strange. So it would be impossible to release co-dependent artifacts? Craig On Aug 10, 2013, at 11:03 AM, Michelle Caisse wrote: Hi all, Preparatory to attempting a release, I cleaned my local repository and did mvn clean install. On building exectck, I got a build error: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) javax.jdo:jdo-api:jar:3.1 This is because, per the apache instructions, our release artifacts have -SNAPSHOT versions, but all dependencies, including the dependency on the api jar that we are in the process of releasing, are to non -SNAPSHOT versions. So, we build jdo-api-3.1-SNAPSHOT.jar, but we are dependent on jdo-api-3.1.jar. What is the best way around this issue? -- Michelle 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!
Documentation for copyjdorijars
The readme file at the trunk or branches/branch level says the following: To run the JDO TCK on the Reference Implementation, copy the following files to the top-level lib/jdori directory. Copy log4j.properties from tck/src/conf. The others may be downloaded from the maven repository. asm-3.0.jar c3p0-0.9.0.2.jar datanucleus-api-jdo-3.0.7.jar datanucleus-api-jpa-3.0.8.jar datanucleus-core-3.0.9.jar datanucleus-enhancer-3.0.1.jar datanucleus-rdbms-3.0.8.jar log4j-1.2.13.jar log4j.properties I believe this is obsolete and copyjdorijars now handles this task. I am not sure, however, if the user has to invoke copyjdorijars or if it gets invoked automatically. I need to update the readme with correct information. -- Michelle
Minutes: JDO TCK Conference Call Friday July 26, 9 am Pacific Daylight Time
Attendees: Michael Bouschen, Michelle Caisse 1. News on JDO-678 Ability to set properties on PersistenceManager: Craig proposed Appendix K https://issues.apache.org/jira/browse/JDO-678 AI: Review. 2. JDO KEYS file http://apache.org/dist/db/jdo/KEYS Michelle scp'ed file from people.apache.org, added her new key and uploaded. 3. JDO release candidate https://issues.apache.org/jira/browse/JDO-723 Everything appears to be ready to go, but there is an issue of version numbering. With the current process using the maven release plug-in, a release is automatically checked in with the specified release number. We cannot change the name from -rc1 once released. We would need to spin a new release with the new version number. So we need to decide on a time and version number for the release and go with it. -- Michelle
[jira] [Closed] (JDO-725) Fix KEYS links per new Apache requirements
[ https://issues.apache.org/jira/browse/JDO-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse closed JDO-725. --- Resolution: Won't Fix Fix Version/s: JDO 3 update 1 (3.0.1) No change is required. We're good. Fix KEYS links per new Apache requirements -- Key: JDO-725 URL: https://issues.apache.org/jira/browse/JDO-725 Project: JDO Issue Type: Task Components: site and infrastructure Reporter: Michelle Caisse Fix For: JDO 3 update 1 (3.0.1) Per Daniel at ASF infra, 5 July: Infra will remove KEYS files from mirrors on Tuesday. Links in download pages to KEYS files should be updated to reference https://www.apache.org/dist/, as per https://www.apache.org/dev/release-download-pages#links second bullet. The JDO download pages, linked to from http://db.apache.org/jdo/downloads.html, must be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-723) Update release process for 3.1
[
https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713289#comment-13713289
]
Michelle Caisse commented on JDO-723:
-
I tried a a dry run of prepare release and got the following error:
$ mvn release:prepare -DdryRun=true -DautoVersionSubmodules=true
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] JDO PARENT
[INFO] JDO API
[INFO] JDO TCK Execution Maven Mojo
[INFO] JDO RI Jar Copy
[INFO] JDO Technology Compatibility Kit (TCK)
[INFO] JDO Root POM
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO]
[INFO] Building JDO Root POM
[INFO]task-segment: [release:prepare] (aggregator-style)
[INFO]
[INFO] [release:prepare {execution: default-cli}]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] You don't have a SNAPSHOT project in the reactor projects list.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jul 18 19:50:31 MST 2013
[INFO] Final Memory: 15M/331M
[INFO]
Update release process for 3.1
--
Key: JDO-723
URL: https://issues.apache.org/jira/browse/JDO-723
Project: JDO
Issue Type: Task
Components: site and infrastructure
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: apache-release.patch
The 3.1 release is the first JDO release using maven 2. In addition the
Apache infrastructure for testing and distributing releases has changed. We
need to update our infrastructure, process, and documents to reflect the new
situation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Correction: JDO TCK Conference Call Friday July 12, 9 am Pacific Daylight Time
Same here. The patch worked for me. -- Michelle On 7/12/2013 4:05 PM, Michael Bouschen wrote: Hi, [...] 1. News on JDO-678 Ability to set properties on PersistenceManager https://issues.apache.org/jira/browse/JDO-678 Michael applied the patch and got one failure but probably unrelated to the patch. I ran the tck with the patch applied again and now all the tests passed. Regards Michael
[jira] [Created] (JDO-725) Fix KEYS links per new Apache requirements
Michelle Caisse created JDO-725: --- Summary: Fix KEYS links per new Apache requirements Key: JDO-725 URL: https://issues.apache.org/jira/browse/JDO-725 Project: JDO Issue Type: Task Components: site and infrastructure Reporter: Michelle Caisse Per Daniel at ASF infra, 5 July: Infra will remove KEYS files from mirrors on Tuesday. Links in download pages to KEYS files should be updated to reference https://www.apache.org/dist/, as per https://www.apache.org/dev/release-download-pages#links second bullet. The JDO download pages, linked to from http://db.apache.org/jdo/downloads.html, must be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-723) Update release process for 3.1
[ https://issues.apache.org/jira/browse/JDO-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700284#comment-13700284 ] Michelle Caisse commented on JDO-723: - I committed Michael's patch with some additional changes. I ported Andy's new DataNucleus version numbers to this branch and added configuration for the deploy plugin to skip the subprojects whose jar files we don't want to deploy. Also added some configuration that allows user-specific injection of key id via settings.xml. Additional issues for discussion: 1. Need to turn of automatic packaging of src? 2. Version numbers for copy-jdori-jars vs. jdo-exectck. 3. Configuration for SCM required for deployment: http://maven.apache.org/pom.html#SCM ... Update release process for 3.1 -- Key: JDO-723 URL: https://issues.apache.org/jira/browse/JDO-723 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: apache-release.patch The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure for testing and distributing releases has changed. We need to update our infrastructure, process, and documents to reflect the new situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Minutes: JDO TCK Conference Call Friday June 28, 9 am Pacific Daylight Time
You can track our Apache infra issue here: https://issues.apache.org/jira/browse/INFRA-6481 -- Michelle On 6/28/2013 10:01 AM, Craig L Russell wrote: AI Michelle submit the JIRA ticket to get jdo into the Nexus repository per instructions on http://www.apache.org/dev/publishing-maven-artifacts.html
wiki spam
The top level apache wiki page has some FAQs regarding spam: http://wiki.apache.org/general/WikiFrequentlyAskedQuestions I think we should discuss some simple actions we can take to avoid spam at the next weekly meeting. -- Michelle
Re: gpg help, please
Thanks for the replies. I think I didn't provide enough information. When I run mvn clean install -Papache-release, it prompts me for my gpg passphrase and I enter it on the command line, where it is masked. After that it gives the error. I think the problem is that, after 5 years and several computer and OS upgrades, I've lost my private key. I will need to create a new key. -- Michelle On 6/24/2013 9:12 PM, Andy Jefferson wrote: I haven't tried this particular profile. The only thing I can think of is that you need to have some other command line parameter to allow maven to get your private (key) password. You cannot pass your password on the command line because anyone who does ps-ef can see your password in the plain. So it has to be some file or you type it into the maven command. It may be that you need to configure the nexus repository to do this. I use the Maven release plugin to release DataNucleus and following the Sonatype guide(s) I ended up editing the users .m2/settings.xml with (something like) profiles profile iddevelopment/id properties gpg.passphraseYOURPASSPHRASE/gpg.passphrase /properties /profile /profiles activeProfiles activeProfiledevelopment/activeProfile /activeProfiles and so I never have to enter the passphrase at release. HTH
gpg help, please
Following the instructions at http://www.apache.org/dev/publishing-maven-artifacts.html, I have downloaded gnupg and run mvn clean install -Papache-release I get a gpg error: gpg: no default secret key: No secret key gpg: signing failed: No secret key How do I configure gpg or point it to a default secret key, or whatever? Thanks, Michelle
Wiki statistics
If you scroll to the bottom of the front page https://wiki.apache.org/jdo/FrontPage, you will find links to special pages, including Hit counts https://wiki.apache.org/jdo/EventStats/HitCounts and User agents https://wiki.apache.org/jdo/EventStats/UserAgents. Another useful page is PageHits https://wiki.apache.org/jdo/PageHits. -- Michelle
[jira] [Created] (JDO-723) Update release process for 3.1
Michelle Caisse created JDO-723: --- Summary: Update release process for 3.1 Key: JDO-723 URL: https://issues.apache.org/jira/browse/JDO-723 Project: JDO Issue Type: Task Components: site and infrastructure Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure for testing and distributing releases has changed. We need to update our infrastructure, process, and documents to reflect the new situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Minutes: JDO TCK Conference Call Friday June 14, 9 am Pacific Daylight Time
Attendees: Michael Bouschen, Michelle Caisse Agenda: 1. News on JDO-678 Ability to set properties on PersistenceManager https://issues.apache.org/jira/browse/JDO-678 No news. 2. JDO release candidate The release will consist of the api jar file and source for api, tck, exectck, copyjdorijars, and all build files, all in one archive file. Maven 2 builds the jar file automatically on mvn package. The trick is to get the source files spanning multiple maven projects into one archive file. Michael will investigare using the maven assembly plug-in for this task. 3. Other issues We have noticed a recent increase in spam pages added to the jdo wiki. We have been deleting them quickly and will discuss if the amount of spam becomes unmanageable. Action items completed: Completed: [May 31 2013] AI Michelle: add an empty Appendix K to put the table into and update the book to include it. Completed with Matthew's email to jdo-user, which Michael forwarded to jdo-dev: [May 10 2013] AI Matthew take a deeper look into the way how JPA defines entity graphs (centralized vs. distributed across the metadata in JDO -- Michelle
Release candidate questions
We have a new structure to the release branch and I'm not sure how to handle it. Do we release the specification source directory, or delete it from branches/3.1-rc1? How do we handle copyjdorijars and exectck? Will we zip them in a source bundle with the tck? What do we do with parent-pom? -- Michelle
Re: svn commit: r1488078 - /db/jdo/trunk/tck/src/java/org/apache/jdo/tck/api/persistencemanager/GetProperties.java
All tests pass for me. -- Michelle
On 5/30/2013 6:44 PM, c...@apache.org wrote:
Author: clr
Date: Fri May 31 01:44:02 2013
New Revision: 1488078
URL: http://svn.apache.org/r1488078
Log:
Add mixed case tests to getProperties tests
Modified:
db/jdo/trunk/tck/src/java/org/apache/jdo/tck/api/persistencemanager/GetProperties.java
Modified:
db/jdo/trunk/tck/src/java/org/apache/jdo/tck/api/persistencemanager/GetProperties.java
URL:
http://svn.apache.org/viewvc/db/jdo/trunk/tck/src/java/org/apache/jdo/tck/api/persistencemanager/GetProperties.java?rev=1488078r1=1488077r2=1488078view=diff
==
---
db/jdo/trunk/tck/src/java/org/apache/jdo/tck/api/persistencemanager/GetProperties.java
(original)
+++
db/jdo/trunk/tck/src/java/org/apache/jdo/tck/api/persistencemanager/GetProperties.java
Fri May 31 01:44:02 2013
@@ -178,6 +178,18 @@ public class GetProperties extends JDO_T
public void set(PersistenceManager pm, Object value)
{pm.setMultithreaded((Boolean) value);}
};
+private TestProperty testLowerCaseMultithreaded =
+new AbstractAPITestProperty(PROPERTY_MULTITHREADED, true, false) {
+public Object get(PersistenceManager pm) {return
pm.getMultithreaded();}
+public void set(PersistenceManager pm, Object value)
{pm.setProperty(javax.jdo.option.multithreaded, (Boolean) value);}
+};
+
+private TestProperty testUpperCaseMultithreaded =
+new AbstractAPITestProperty(PROPERTY_MULTITHREADED, true, false) {
+public Object get(PersistenceManager pm) {return pm.getMultithreaded();}
+public void set(PersistenceManager pm, Object value)
{pm.setProperty(javax.jdo.option.MULTITHREADED, (Boolean) value);}
+};
+
private TestProperty testDetachAllOnCommit =
new AbstractAPITestProperty(PROPERTY_DETACH_ALL_ON_COMMIT, true,
false) {
public Object get(PersistenceManager pm) {return
pm.getDetachAllOnCommit();}
@@ -242,7 +254,8 @@ public class GetProperties extends JDO_T
testRequiredProperties.add(testIgnoreCache);
testRequiredProperties.add(testRestoreValues);
-testOptionalProperties.put(PROPERTY_MULTITHREADED, setOf(testMultithreaded));
+testOptionalProperties.put(PROPERTY_MULTITHREADED,
setOf(testMultithreaded, testLowerCaseMultithreaded,
+testUpperCaseMultithreaded));
testOptionalProperties.put(OPTION_DATASTORE_TIMEOUT,
setOf(testDatastoreReadTimeoutMillis,
testDatastoreWriteTimeoutMillis));
testOptionalProperties.put(PROPERTY_OPTIMISTIC,
setOf(testOptimistic));
Re: Minutes: JDO TCK Conference Call Friday May 24, 9 am Pacific Daylight Time
Matthew Adams also attended. -- Michelle On 5/24/2013 9:57 AM, Craig L Russell wrote: Attendees: Michelle Caisse, Michael Bouschen, Craig Russell Agenda: 1. TCK query test failure: possible time zone issue in SupportedDateMethods: https://issues.apache.org/jira/browse/JDO-720 It almost appears to work. AI Michael check in the patch since it seems to work. 2. News on JDO-678 Ability to set properties on PersistenceManager https://issues.apache.org/jira/browse/JDO-678 Still almost done. 3. Other issues Volunteers to roll the release? Michelle volunteered. The release that doesn't need any JCP approval would be jdo-3.1-rc1. Action Items from weeks past: [May 10 2013] AI Everyone take a look Apache ISIS and maybe subscribe to ISIS mail lists. [May 10 2013] AI Matthew take a deeper look into the way how JPA defines entity graphs (centralized vs. distributed across the metadata in JDO) [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [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-720) Possible time zone issue in SupportedDateMethods
[ https://issues.apache.org/jira/browse/JDO-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666923#comment-13666923 ] Michelle Caisse commented on JDO-720: - Works for me. However my total tests run was 1800. I thought there were actually a few more than that. But the jdoql SupportedDateMethods tests did run and pass. Possible time zone issue in SupportedDateMethods Key: JDO-720 URL: https://issues.apache.org/jira/browse/JDO-720 Project: JDO Issue Type: Bug Components: tck Affects Versions: JDO 3 update 1 (3.0.1) Reporter: Michael Bouschen Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-720.patch The TCK query test SupportedDateMethods fails when running a Date.getDate query: the query result is empty where it should include an employee instacne. Please note, the failure occurs when running the test in California and Arizona, but not in Europe. Looks like the problem is in the company model reader creating a date in the America/New_York time zone that is actually yesterday in other time zones, so the tests fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-720) Possible time zone issue in SupportedDateMethods
[
https://issues.apache.org/jira/browse/JDO-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13665958#comment-13665958
]
Michelle Caisse commented on JDO-720:
-
I get error info in trunk/tck/target/logs/timestamp/app-jdoql-junit.txt and
.../dsid-jdoql-junit.txt (not to be confused with ...jdoql1-junit.txt).
There was 1 failure:
1)
testGetDate(org.apache.jdo.tck.query.jdoql.methods.SupportedDateMethods)junit.framework.AssertionFailedError:
Assertion A14.6.2-60 (SupportedDateMethods) failed:
Wrong query result:
query: SELECT FROM org.apache.jdo.tck.pc.company.Person WHERE
birthdate.getDate() == 10
expected: java.util.ArrayList of size 1
[FullTimeEmployee(1, emp1Last, emp1First, born 9/Jun/1970, phone
{work=123456-1, home=}, hired 31/Dec/1998, weeklyhours 40.0, $2.0)]
got: java.util.ArrayList of size 0
[]
at org.apache.jdo.tck.JDO_Test.fail(JDO_Test.java:719)
at org.apache.jdo.tck.query.QueryTest.queryFailed(QueryTest.java:518)
at
org.apache.jdo.tck.query.QueryTest.checkQueryResultWithoutOrder(QueryTest.java:548)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1293)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1133)
at
org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:1069)
at
org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:1049)
at
org.apache.jdo.tck.query.jdoql.methods.SupportedDateMethods.executeQuery(SupportedDateMethods.java:143)
at
org.apache.jdo.tck.query.jdoql.methods.SupportedDateMethods.testGetDate(SupportedDateMethods.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284)
at
org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
at
org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
at
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
FAILURES!!!
Possible time zone issue in SupportedDateMethods
Key: JDO-720
URL: https://issues.apache.org/jira/browse/JDO-720
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 update 1 (3.0.1)
Reporter: Michael Bouschen
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: JDO-720.patch
The TCK query test SupportedDateMethods fails when running a Date.getDate
query: the query result is empty where it should include an employee
instacne.
Please note, the failure occurs when running the test in California and
Arizona, but not in Europe.
Looks like the problem is in the company model reader creating a date in the
America/New_York time zone that is actually yesterday in other time zones, so
the tests fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Minutes: JDO TCK Conference Call Friday May 17, 9 am Pacific Daylight Time
I applied the patch and ran the TCK and the test still fails for me.
19:01:07,709 (main) INFO [org.apache.jdo.tck] - Exception during setUp
or runtest:
junit.framework.AssertionFailedError: Assertion A14.6.2-60
(SupportedDateMethods) failed:
Wrong query result:
query: SELECT FROM org.apache.jdo.tck.pc.company.Person WHERE
birthdate.getDate() == 10
expected: java.util.ArrayList of size 1
[FullTimeEmployee(1, emp1Last, emp1First, born 9/Jun/1970, phone
{work=123456-1, home=}, hired 31/Dec/1998, weeklyhours 40.0, $2.0)]
got: java.util.ArrayList of size 0
[]
at junit.framework.Assert.fail(Assert.java:47)
at org.apache.jdo.tck.JDO_Test.fail(JDO_Test.java:719)
at org.apache.jdo.tck.query.QueryTest.queryFailed(QueryTest.java:518)
at
org.apache.jdo.tck.query.QueryTest.checkQueryResultWithoutOrder(QueryTest.java:548)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1293)
at org.apache.jdo.tck.query.QueryTest.execute(QueryTest.java:1133)
at
org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:1069)
at
org.apache.jdo.tck.query.QueryTest.executeAPIQuery(QueryTest.java:1049)
at
org.apache.jdo.tck.query.jdoql.methods.SupportedDateMethods.executeQuery(SupportedDateMethods.java:143)
at
org.apache.jdo.tck.query.jdoql.methods.SupportedDateMethods.testGetDate(SupportedDateMethods.java:118)
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 junit.framework.TestCase.runTest(TestCase.java:154)
at org.apache.jdo.tck.JDO_Test.runBare(JDO_Test.java:284)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.textui.TestRunner.doRun(TestRunner.java:116)
at
org.apache.jdo.tck.util.BatchTestRunner.doRun(BatchTestRunner.java:108)
at
org.apache.jdo.tck.util.BatchTestRunner.start(BatchTestRunner.java:148)
at
org.apache.jdo.tck.util.BatchTestRunner.main(BatchTestRunner.java:123)
-- Michelle
On 5/19/2013 1:44 PM, Michael Bouschen wrote:
Hi,
[...]
1. TCK query test failure: possible time zone issue in
SupportedDateMethods: https://issues.apache.org/jira/browse/JDO-720
Still fails in time zones west of GMT. It looks like there is a
mismatch between java Date types and database Timestamp type.
Timestamps are generally stored in UTC regardless of the location of
the client. So when querying for DAY in the database we would have to
know what the day is in UTC. Propose changing the database type to
DATE and see if that has any effect. AI Michael change database type
to DATE.
I attached a patch to the JIRA:
https://issues.apache.org/jira/browse/JDO-720
It includes all the changes from the previous patch
TimeZoneChanges.patch (removing the time zone setting) plus it changes
the column type from TIMSTAMP to DATE for the columns HIREDATE,
BIRTHDATE and FOUNDEDDATE.
Regards Michael
[jira] [Commented] (JDO-719) JDOQL should support Date.getDate instead of Date.getDay
[ https://issues.apache.org/jira/browse/JDO-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13626186#comment-13626186 ] Michelle Caisse commented on JDO-719: - I installed the patch and ran the TCK. The test still fails for me. The comment containing the method name being tested should also be changed from getDay to getDate. JDOQL should support Date.getDate instead of Date.getDay Key: JDO-719 URL: https://issues.apache.org/jira/browse/JDO-719 Project: JDO Issue Type: Bug Components: specification, tck Affects Versions: JDO 3 maintenance release 1 (3.1) Reporter: Michael Bouschen Assignee: Michael Bouschen Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-719.patch JDO-658 proposed support for more methods in JDOQL. It's clear reading the description of getDay that this is not the api that was intended. It should be changed to getDate instead. This is probably not a backward compatibility issue since the new query api is included in 3.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Minutes: JDO TCK Conference Call Friday April 5, 9 am Pacific Daylight Time
This test case is failing consistently for me. I've run it 5 times over two days. I'm in GMT - 8, Mountain Standard Time. -- Michelle On 4/5/2013 7:10 PM, Craig L Russell wrote: ... a) The test case failure may be a time zone issue. The test case is written so as to use the East Coast time zone (GMT - 5:00). There are intermittent failures running the test with GMT - 8:00. But no failures running GMT + 1. AI Craig code review the test case.
Re: JDO TCK Conference Call Friday February 8, 9 am Pacific Time
Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams 1. News on JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717 No change. 2. News on JDO-678 Ability to set properties on PersistenceManager https://issues.apache.org/jira/browse/JDO-678 Craig will change spec. A test case may be needed. 3. News on spec update? No news. 4. Other issues Social media links - Text links to JDO Facebook, Twitter, and Google+ pages now exist on db.apache.org/jdo on the top navbar of all pages. Matthew will look into marketing our presence to drum up more activity and participation. Action Items from weeks past: [Nov 02 2012] AI Craig JDO-678 needs a test case. In process. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. In process. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
Spec Appendix A needs work
Just a note that we need to take a look at Appendix A and do some clean-up. -- Michelle
Re: JDO social links
I added text links to these sites to db.apache.org/jdo, but Facebook and Twitter require that the page owner create a badge to allow a ink using the ubiquitous graphic widget. -- Michelle On 7/20/2012 11:23 AM, Matthew Adams wrote: Facebook: https://www.facebook.com/JavaDataObjects Twitter: @JavaDataObjects Google+: https://plus.google.com/s/javadataobjects
Re: Minutes: JDO TCK Conference Call Friday January 11, 9 am Pacific Time
On 1/14/2013 1:19 AM, Andy Jefferson wrote: Yes, Maven seemingly also looks under xdocs for documents to render on the site (not mentioned in its docs), as well as the standard location (mentioned in all its docs of src/site). Just move the existing Maven1-based xdocs to a different location and then run mvn site. The intention is to delete that directory when it is generated to people's satisfaction. I've also updated it now to not generate various mindless Maven reports that don't appear on the site. Andy, thanks. It runs fine with xdocs moved and produces good output. Does docs/navigation.html need to be svn added? I do get a lot of warnings like this: [WARNING] [XHTML Sink] No HTML tag found for unknown event: 'B', ignoring! -- Michelle
Re: Minutes: JDO TCK Conference Call Friday January 11, 9 am Pacific Time
On 1/13/2013 10:09 AM, Andy Jefferson wrote: 1. Problem building site There is still an issue with building the site. Seems to be a maven repository variable issue reported as a missing dependency. The site is published as it existed a few months ago but can't be updated (generated) as the instructions in site/HOWTO don't currently work. maven.repo.remote needs to be set. Does anyone know how to fix this? Not used Maven1 in some time and don't know what the problem is, but I could try converting it to Maven2+ so then there is no requirement for Maven1 in the Apache JDO project. I did the same for DataNucleus docs a while back. Any objections ? I've checked into SVN the Maven2 site. This is comprised of src/ directory, including all xdocs and resources as before, but with XSD's defined and formatting updated so they match XSD. pom.xml Just do mvn clean site and it generates the site under target/site. If people can try it and see if it works for everyone, then I can delete the old xdocs directory as well as maven.xml, project.xml, project.properties I get an error building the site: 7K downloaded (maven-default-skin-1.0.jar) [INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0 skin. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Files 'xdoc\attach_detach.xml' clashes with existing 'C:\jdo\site\src\site\xdoc\attach_detach.xml'. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 33 seconds [INFO] Finished at: Sun Jan 13 18:29:47 MST 2013 [INFO] Final Memory: 46M/528M [INFO]
Re: Minutes: JDO TCK Conference Call Friday January 11, 9 am Pacific Time
On 1/13/2013 6:35 PM, Michelle Caisse wrote: On 1/13/2013 10:09 AM, Andy Jefferson wrote: 1. Problem building site There is still an issue with building the site. Seems to be a maven repository variable issue reported as a missing dependency. The site is published as it existed a few months ago but can't be updated (generated) as the instructions in site/HOWTO don't currently work. maven.repo.remote needs to be set. Does anyone know how to fix this? Not used Maven1 in some time and don't know what the problem is, but I could try converting it to Maven2+ so then there is no requirement for Maven1 in the Apache JDO project. I did the same for DataNucleus docs a while back. Any objections ? I've checked into SVN the Maven2 site. This is comprised of src/ directory, including all xdocs and resources as before, but with XSD's defined and formatting updated so they match XSD. pom.xml Just do mvn clean site and it generates the site under target/site. If people can try it and see if it works for everyone, then I can delete the old xdocs directory as well as maven.xml, project.xml, project.properties I get an error building the site: 7K downloaded (maven-default-skin-1.0.jar) [INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0 skin. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Files 'xdoc\attach_detach.xml' clashes with existing 'C:\jdo\site\src\site\xdoc\attach_detach.xml'. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 33 seconds [INFO] Finished at: Sun Jan 13 18:29:47 MST 2013 [INFO] Final Memory: 46M/528M [INFO] When I delete xdocs locally, it all works. It appears, though, that there are a few files generated in target/site that are unversioned in docs, for example license.html. That may be a pre-existing problem. -- Michelle
Re: JDO TCK Conference Call Friday Dezember 21, 9 am Pacific Time
I am unable to attend the meeting today. Status update on agenda item 1, Mandatory svnpubsub migration: - Docs are checked into the db tree at https://svn.apache.org/repos/infra/websites/production/db/content/jdo - Everything is ready for all the db projects to go live. Rick Hillegas has submitted the JIRA issue to request that we go live (https://issues.apache.org/jira/browse/INFRA-5696). - I added a svn:externals property to the site tree in svn, which should allow us to continue to use the existing site build mechanism essentially unchanges, except that the step of logging onto the apache server and running a script is no longer necessary. Due to the problem building ste and lack of time, the full cycle of modifying content has not been tested. -- Michelle On 12/20/2012 1:51 PM, Michael Bouschen wrote: Hi, We will have our regular meeting Friday, Dezember 21 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. Mandatory svnpubsub migration by Jan 2013 2. Problem building site 3. News on JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717 4. News on spec update? 5. Other issues Action Items from weeks past: [Dec 07 2012] AI Craig: Last technical item is still the new assertion needed for Chapter 12. [Nov 16 2012] AI Everybody Cross references to other sections should use parentheses. Maybe we should avoid making this change until we have reviewed and approved the 3.1 changes. Chapters that are not affected by 3.1 could have the bracket-to-parens change made any time, with no requirement to record changes. [Nov 02 2012] AI Craig JDO-678 needs a test case. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Jul 20 2012] AI Michelle: take a look into adding JDO social links to db.apache.org/jdo. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck. Regards Michael
Problem building site
I have a missing dependency when I try to build the JDO site. There doesn't appear to be a version at the Batik site download site that corresponds to the one specified in the output below. $ maven site __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1 build:start: site: xdoc:register-reports: maven-javadoc-plugin:register: site:run-reports: Trying to get missing dependencies (and updated snapshots) required by Maven PDF Plugin: - Attempting to download batik:batik:1.5-fop-0.20-5:jar from http://repo1.maven. org/maven --- Unable to obtain goal [site] The build cannot continue because of the following unsatisfied dependency: - batik:batik:1.5-fop-0.20-5:jar (try downloading from http://xmlgraphics.apache .org/batik/) --- BUILD FAILED --- Total time : 1 seconds Finished at : Monday, December 17, 2012 8:30:32 PM MST Final Memory : 6M/183M --- -- Michelle
Re: JDO TCK Conference Call Friday Dezember 14, 9 am Pacific Time
On 12/14/2012 10:39 AM, Craig L Russell wrote: Attendees: Michelle Caisse, Michael Bouschen, Craig Russell Agenda: 1. Mandatory svnpubsub migration by Jan 2013 We can continue to use our build process but the destination of the site build may need to be in a different svn location. INFRA-5404 and INFRA-5215 are the DB issues for the migration. The generated site has to be svn.apache.org/repos/infra/websites/production/db/jdo and this should automatically propagate to the live web. I've made all the required changes, but the site is not yet live from the new infra/websites location. I think it just needs https://svn.apache.org/repos/asf/db/site-cms/trunk/content/extpaths.txt. I'm not sure if there are any other gating factors. -- Michelle 2. New patch available for JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717 Looks good. Might be good to add a version number to the maven-clean-plugin component. 3. News on spec update? Still stuck on Craig's Need to add an assertion id to Chapter 12. 4. Other issues Action Items from weeks past: [Dec 07 2012] AI Craig: Last technical item is still the new assertion for JDO-678 needed for Chapter 12. [Nov 16 2012] AI Everybody Cross references to other sections should use parentheses. Maybe we should avoid making this change until we have reviewed and approved the 3.1 changes. Chapters that are not affected by 3.1 could have the bracket-to-parens change made any time, with no requirement to record changes. [Nov 02 2012] AI Craig JDO-678 needs a test case. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Jul 20 2012] AI Michelle: take a look into adding JDO social links to db.apache.org/jdo. [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!
Use of brackets in documents
On the telecon this morning, we discussed how square brackets are used in the spec, other than in the hidden assertion markers. In some cases, the spec uses brackets around an internal cross reference, as in [see Chapter 5]. I checked several on-line style guides for information about the use of brackets in writing. http://www.apastyle.org/learn/faqs/use-brackets.aspx http://data.grammarbook.com/blog/brackets/changing-a-quote-using-brackets/ The most similar case presented in these sources is the use of brackets for references, but that is strictly for a reference that provides a key to bibliographic entries that are listed elsewhere in the document. IMHO, it would be more in accord with standard usage to use parentheses instead of square brackets for internal cross references in the spec. This would alleviate potential confusion with the brackets in assertion markers when using a script to extract assertions. -- Michelle
Re: Minutes: JDO TCK Conference Call Friday November 2, 9 am Pacific Time
On 11/2/2012 9:53 AM, Craig L Russell wrote: Attendees: Michael Bouschen, Craig Russell and Michelle Caisse Agenda: 1. News on JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717? no change. 2. News on spec update? Some formatting changes in the master document. Fixed bookmarks and index. 3. Need to check the specification for assertions for new test cases that were added. We should review all resolved issues and make sure that new tests have assertions that match the specification. no change. AI Michael update the assertions for Chapter 14. 4. Other issues JDO-702 is now resolved. JDO-678 needs a test case. AI Craig. Action Items from weeks past: [Sep 7 2012] AI Everybody We need to look at adding assertions into the specification and tck test cases. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Jul 20 2012] AI Michelle: take a look into adding JDO social links to db.apache.org/jdo. [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!
JDO TCK Conference Call Friday October 5, 9 am Pacific Time
On 9/27/2012 10:45 PM, Michael Bouschen wrote: Hi, We will have our regular meeting Friday, October 5 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. News on JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717? 2. News on spec update? 3. Other issues Action Items from weeks past: [Sep 7 2012] AI Everybody We need to look at adding assertions into the specification and tck test cases. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Jul 20 2012] AI Michelle: take a look into adding JDO social links to db.apache.org/jdo. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
Minutes: JDO TCK Conference Call Friday, September 28, 9 am Pacific Time
Attendees: Matthew Adams, Michael Bouschen, Michelle Caisse 1. News on patch JDO-707 https://issues.apache.org/jira/browse/JDO-707? (Refactor JDO parent child poms) Reviewed the patch, and with a fix uploaded by Matthew, was approved. 2. News on JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717? When 707 is checked in (very soon), Matthew will begin work on this. 3. News on spec update? None 4. Other issues Discussion of using git in place of svn. There may be a way to use git with the existing Apache svn server, deferring a move to GitHub. Action Items from weeks past: [Sep 7 2012] AI Everybody We need to look at adding assertions into the specification and tck test cases. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Jul 20 2012] AI Michelle: take a look into adding JDO social links to db.apache.org/jdo. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
Re: Minutes: JDO TCK Conference Call Friday, July 27, 9 am Pacific Time
On 7/27/2012 9:43 AM, Craig L Russell wrote: [Jul 13 2012] AI Michelle see about changing the style in the spec. I think this had to do with figure and/or table captions and their relative location. I checked and captions are at the top of figures and tables, as they were in the Frame version. So I believe no further action is needed. -- Michelle
[jira] [Commented] (JDO-716) Convert spec to OpenOffice
[ https://issues.apache.org/jira/browse/JDO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13404663#comment-13404663 ] Michelle Caisse commented on JDO-716: - Spec has been checked in.Have at it. Please read README.odt!! Some glitches remain: - Blank page 1 - Appendices continue chapter numbering rather than switching to letter names. - Some headings have numbers appended to them. These are easily found and removed by creating pdf and scanning the bookmarks, then editing the chapter file. I haven't done that yet. - Some images have migrated away from their captions. I had trouble with header and footer text disappearing after some changes to the template. Fortunately, it's easy to restore. The problem with autonumbering of section headings is fixed. Convert spec to OpenOffice -- Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse Assignee: Michelle Caisse Attachments: OOO.jar To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- 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-716) Convert spec to OpenOffice
[ https://issues.apache.org/jira/browse/JDO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13403677#comment-13403677 ] Michelle Caisse commented on JDO-716: - Spec writers should download Apache Open Office 3.4 from http://www.openoffice.org/download/ and then download and install the Template Changer extension http://extensions.services.openoffice.org/project/templatechanger in case you need to make style changes to the template. Convert spec to OpenOffice -- Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse Assignee: Michelle Caisse Attachments: OOO.jar To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- 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] [Assigned] (JDO-716) Convert spec to OpenOffice
[ https://issues.apache.org/jira/browse/JDO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse reassigned JDO-716: --- Assignee: Michelle Caisse Convert spec to OpenOffice -- Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse Assignee: Michelle Caisse To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- 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-716) Convert spec to OpenOffice
Michelle Caisse created JDO-716: --- Summary: Convert spec to OpenOffice Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- 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-716) Convert spec to OpenOffice
[ https://issues.apache.org/jira/browse/JDO-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse updated JDO-716: Attachment: OOO.jar The attached file includes all of the book files for the specification on OpenOffice format, including an empty master file and a template file. All chapters use the included template. Convert spec to OpenOffice -- Key: JDO-716 URL: https://issues.apache.org/jira/browse/JDO-716 Project: JDO Issue Type: Improvement Components: specification Reporter: Michelle Caisse Assignee: Michelle Caisse Attachments: OOO.jar To support collaborative writing and use openly available tools, we will convert the specification document from FrameMaker to OpenOffice. -- 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
Re: JDO TCK Conference Call Friday, June 8
I can't make the meeting. Here's an update on conversion of the spec from FrameMaker to OpenOffice: Using mif2go, I have converted to rtf. As recommended by mif2go, I have converted the rtf to .docx format using Word. It looks good in Word, as far as I have been able to tell. Some chapters do not look good when the docx file is opened in OpenOffice; most look fine. Opening the rtf directly in OpenOffice gives very poor results. Next step is to split the document into separate files per chapter and create a master document. My first attempt didn't work so well, but I will try again. -- Michelle On 6/7/2012 8:07 PM, Craig L Russell wrote: Sorry for the late notice. I will not be able to attend this week. If you want to hold the meeting, those who know the conference host password, it has been changed. s/122/133. See you next week. Craig 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!
Re: Minutes: JDO TCK Conference Call Friday, May 25, 9 am Pacific Time
Worked fine for me. I applied the patch and did mvn clean install. -- Michelle On 5/28/2012 1:02 PM, Michael Bouschen wrote: Hi, 1. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/jira/browse/JDO-706 Michael suggests a new copyjdorijars with a plugin copyfiles that would copy jars from the dependencies location to the jdori/lib directory. The project would be an independent project that would be downloaded independent of the tck project and exectck project. AI Michael provide a patch. attached you find a patch creating a new module copyjdorijars and adds this to the list of mdules in the root pom. Please have a look. Regards Michael -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
Re: Minutes: JDO TCK Conference Call Friday, May 18, 9 am Pacific Time
I like the name copyjdorijars. Can it also copy log4j.properties to lib/jdori? -- Michelle On 5/20/2012 11:48 AM, Michael Bouschen wrote: Hi, We now assume that the necessary jars to run the RI need to be copied to the user's jdori lib directory. Is there an easier way than manual copying to get the jar files into the right place? AI Michael investigate some other way to copy the jar files. the maven-dependency-plugin allows to copy all the dependencies in a specified location. I propose to add a new module parallel to api, exectck and tck. It will have the datanucleus jars as dependencies and the only purpose is to copy these jars into lib/jdori. I'm looking for a good name for such a module, for now I use copyjdorijars. Does anybody have a better idea for a name? I will provide a patch, as soon as I have a good name. Regards Michael
[jira] [Commented] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279397#comment-13279397
]
Michelle Caisse commented on JDO-706:
-
Modified patch checked in.
The issue remains open in the hope of finding a way to make it easier for users
to obtain the jars that now must be manually copied to lib/jdori.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: jdo-706.patch
Patch removes connection pooling jars from maven dependencies, updates
README.html
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo-706.patch, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Commented] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274375#comment-13274375
]
Michelle Caisse commented on JDO-706:
-
The patch (with some modifications) has been checked in, along with changes to
AbstractGetPMF to fix the test errors due to mismatched file separator
characters. To run the TCK, you must place the following files (or latest
versions thereof) in the top-level lib/jdori:
asm-3.0.jar
datanucleus-core-3.0.9.jar
log4j-1.2.13.jar
datanucleus-api-jdo-3.0.7.jar
datanucleus-enhancer-3.0.1.jar
log4j.properties
datanucleus-api-jpa-3.0.8.jar
datanucleus-rdbms-3.0.8.jar
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: (was: jdo706.patch)
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Commented] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13255701#comment-13255701
]
Michelle Caisse commented on JDO-706:
-
Andy's guess that the issues on Windows have to do with its limitation on
command length appears to be a good one. With a web search I find this, for
example:
When I launch our application in Eclipse on Windows I receive the following
error:
Exception occured executing command line.
Cannot run program .. : CreateProcess error=87, The parameter is incorrect
I've solved this in the past by shortening the CLASSPATH.
I've now come to a point where I can no longer shorten the CLASSPATH, and would
like to know if there are any other workarounds.
http://support.microsoft.com/kb/830473 seems to indicate that the max command
prompt line length in windows xp is 8191 characters, and the only solution is
to shorten folder names, reduce depth of folder trees, using parameter files,
etc.
exectck displays the command line for each test, so we can check that and see
what might be truncated for the failing tests.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Commented] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13253570#comment-13253570
]
Michelle Caisse commented on JDO-706:
-
Running with correct versions of jars in top level lib/jdori/ resolves most,
but not all test errors.
asm-3.0.jar, datanucleus-core-3.0.9.jar, log4j-1.2.13.jar.
datanucleus-api-jdo-3.0.7.jar, datanucleus-enhancer-3.0.1.jar,
log4j.properties,datanucleus-api-jpa-3.0.8.jar datanucleus-rdbms-3.0.8.jar
Still observer errors on pmf test, failure on jdoql test.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: (was: jdo706.patch)
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: 20120410-211429.zip
I get the same errors with java 1.6.0_25. Error log files attached.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
Attachments: 20120410-211429.zip, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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
Re: API build failure
The patch fixed the problem I reported, but revealed the same issue with
two files in test. With the following patch, api compiles and builds
with Java 1.7:
Index: api/src/java/javax/jdo/spi/JDOImplHelper.java
===
--- api/src/java/javax/jdo/spi/JDOImplHelper.java(revision 1308201)
+++ api/src/java/javax/jdo/spi/JDOImplHelper.java(working copy)
@@ -839,7 +839,7 @@
public static Object construct(String className, String keyString) {
StringConstructor stringConstructor;
try {
-Class keyClass = Class.forName(className);
+Class? keyClass = Class.forName(className);
synchronized(stringConstructorMap) {
stringConstructor =
(StringConstructor)
stringConstructorMap.get(keyClass);
@@ -847,8 +847,8 @@
if (stringConstructor != null) {
return stringConstructor.construct(keyString);
} else {
-Constructor keyConstructor =
-keyClass.getConstructor(new Class[]{String.class});
+Constructor? keyConstructor =
+keyClass.getConstructor(new Class?[]{String.class});
return keyConstructor.newInstance(new
Object[]{keyString});
}
} catch (JDOException ex) {
Index: api/test/java/javax/jdo/ObjectStateTest.java
===
--- api/test/java/javax/jdo/ObjectStateTest.java(revision 1308201)
+++ api/test/java/javax/jdo/ObjectStateTest.java(working copy)
@@ -215,7 +215,7 @@
}
private static Method getDeclaredMethod
-(Class clazz, String methodName, Class[] parameters) {
+(Class? clazz, String methodName, Class[] parameters) {
try {
Method result = clazz.getDeclaredMethod(methodName,
parameters);
return result;
Index: api/test/java/javax/jdo/util/BatchTestRunner.java
===
--- api/test/java/javax/jdo/util/BatchTestRunner.java(revision 1308201)
+++ api/test/java/javax/jdo/util/BatchTestRunner.java(working copy)
@@ -111,10 +111,10 @@
String msg = null;
try {
// get class instance
-Class clazz = Class.forName(className);
+Class? clazz = Class.forName(className);
// constructor taking PrintStream arg
-Constructor ctor = clazz.getConstructor(
-new Class[] { PrintStream.class } );
+Constructor? ctor = clazz.getConstructor(
+new Class?[] { PrintStream.class } );
// create instance
return (ResultPrinter)ctor.newInstance(
new Object[] { System.out });
-- Michelle
On 4/2/2012 8:01 AM, Craig L Russell wrote:
Can you try this patch?
Your symptom is probably a bug in JDK 1.7...
Craig
Index: src/java/javax/jdo/spi/JDOImplHelper.java
===
--- src/java/javax/jdo/spi/JDOImplHelper.java(revision 1307510)
+++ src/java/javax/jdo/spi/JDOImplHelper.java(working copy)
@@ -839,7 +839,7 @@
public static Object construct(String className, String keyString) {
StringConstructor stringConstructor;
try {
-Class keyClass = Class.forName(className);
+Class? keyClass = Class.forName(className);
synchronized(stringConstructorMap) {
stringConstructor =
(StringConstructor)
stringConstructorMap.get(keyClass);
@@ -847,8 +847,8 @@
if (stringConstructor != null) {
return stringConstructor.construct(keyString);
} else {
-Constructor keyConstructor =
-keyClass.getConstructor(new Class[]{String.class});
+Constructor? keyConstructor =
+keyClass.getConstructor(new
Class?[]{String.class});
return keyConstructor.newInstance(new
Object[]{keyString});
}
} catch (JDOException ex) {
On Apr 2, 2012, at 12:56 AM, Michael Bouschen wrote:
Hi Michelle,
do you have a JDK1.6 installed and can rebuild the api with JDK1.6?
I'm wondering whether this makes a difference.
Regards Michael
With a clean check-out of JDO trunk, using jdk1.7.0_03, I get a
build error:
[INFO] Compilation failure
could not parse error message: warning: [options] bootstrap class
path not set in conjunction with -source 1.5
C:\jdoClean\api\src\java\javax\jdo\spi\JDOImplHelper.java:851:
warning: [unchecked] unchecked call to getConstructor(Class?...)
as a member of the raw type Class
keyClass.getConstructor(new Class[]{String.class});
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: jdo706.patch
Runs with errors. 11/91 configurations fail. 7 failures, 34 errors out of 1724
tests. Repeated error:
Error moving implementation log file Failed to delete original file
'C:\jdo_newest\datanucleus.txt' after copy to
'C:\jdo_newest\tck\target\logs\...-jdori.txt'
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Attachments: jdo706.patch, jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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
API build failure
With a clean check-out of JDO trunk, using jdk1.7.0_03, I get a build
error:
[INFO] Compilation failure
could not parse error message: warning: [options] bootstrap class path
not set in conjunction with -source 1.5
C:\jdoClean\api\src\java\javax\jdo\spi\JDOImplHelper.java:851: warning:
[unchecked] unchecked call to getConstructor(Class?...) as a member of
the raw type Class
keyClass.getConstructor(new Class[]{String.class});
^
-- Michelle
michelle@michelle-PC /cygdrive/c/jdoClean
$ mvn clean install
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Java Data Objects (JDO)
[INFO] JDO API
[INFO] jdo-exectck Maven Mojo
[INFO] JDO 3 Technology Compatibility Kit
[INFO]
[INFO] Building Java Data Objects (JDO)
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus
.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing C:\jdoClean\pom.xml to
C:\Users\michelle\.m2\repository\javax\
jdo\root\3.1-SNAPSHOT\root-3.1-SNAPSHOT.pom
[INFO]
[INFO] Building JDO API
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource to META-INF
[INFO] Copying 1 resource
[INFO] Copying 31 resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 146 source files to C:\jdoClean\api\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
could not parse error message: warning: [options] bootstrap class path
not set i
n conjunction with -source 1.5
C:\jdoClean\api\src\java\javax\jdo\spi\JDOImplHelper.java:851: warning:
[uncheck
ed] unchecked call to getConstructor(Class?...) as a member of the raw
type Cl
ass
keyClass.getConstructor(new Class[]{String.class});
^
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Sun Apr 01 13:59:15 MST 2012
[INFO] Final Memory: 41M/530M
[INFO]
michelle@michelle-PC /cygdrive/c/jdoClean
$ echo $JAVA_HOME
C:\Program Files\Java\jdk1.7.0_03
Re: Minutes: JDO TCK Conference Call Friday, Mar 16, 9 am Pacific Time
A few minor suggestions on README.html: 1. 2. In Running the TCK, put a space in identity types and omit the comma before or in the last sentence. 3. Move the Note at the bottom of the document to the end of the Custom Goals section. 4. Last line in Command Line Options section needs a space in and error output. 5. Move the Examples section up to immediately follow Command Line Options. 6. Files section needs a little more context. Maybe saying While running the TCK, maven uses the following configuration files in src/conf: is better. -- Michelle On 3/23/2012 9:30 AM, Michael Bouschen wrote: Hi, and now as zip-dile. Regards Michael Hi, attached you find the README.html. Regards Michael Hi, Attendees: Michael Bouschen, Michelle Caisse, Craig Russell Agenda: 1. README.html under trunk needs to be reviewed. Maven: need at least maven 2 to build. But should we remove the reference to mevenide? Yes. AI Michael send a patch with more review. attached you find a patch updating the README.html. Please have a look. Regards Michael -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680 -- *Michael Bouschen* *Prokurist* akquinet tech@spree GmbH Bülowstr. 66, D-10783 Berlin Fon: +49 30 235 520-33 Fax: +49 30 217 520-12 Email: michael.bousc...@akquinet.de Web: www.akquinet.de http://www.akquinet.de akquinet tech@spree GmbH, Berlin Geschäftsführung: Martin Weber, Dr. Torsten Fink Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680
[jira] [Updated] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Caisse updated JDO-706:
Attachment: jdo706.patch
Uploading a patch for safekeeping. This doesn't yet work, but I think it's
close.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
Attachments: jdo706.patch
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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
Re: [jira] [Commented] (JDO-706) No enhancer log output with maven 2
The context class loader contains tck/target/classes and either
lib/jdori or lib/iut, which is the location of log4j.properties works
for enhancement. The enhancer seems to need the ASM jar file in the same
loader as the classes to be enhanced. So at this point, I'm only using
one classloader both to get the enhancer and to configure the enhancer.
So far, so good, but more testing is needed.
-- Michelle
On 3/25/2012 9:42 AM, Craig L Russell wrote:
Very Cool!
So what is the class loader configuration that makes it all work? Is
the solution portable to iut?
Craig
On Mar 24, 2012, at 5:28 PM, Michelle Caisse (Commented) (JIRA) wrote:
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237742#comment-13237742
]
Michelle Caisse commented on JDO-706:
-
I have enhancement working with no errors or warnings now. I need to
include tck/target/classes on the classpath. Without it, log4j
complains that it can't find org.apache.jdo.tck.util.TCKFileAppender
and the ri enhancer complains that it can't find
org/apache/jdo/tck/util/DeepEquality.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
No log output for enhancement is produced. The following warnings
are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger
(DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to
the log properties 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
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-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13237742#comment-13237742
]
Michelle Caisse commented on JDO-706:
-
I have enhancement working with no errors or warnings now. I need to include
tck/target/classes on the classpath. Without it, log4j complains that it can't
find org.apache.jdo.tck.util.TCKFileAppender and the ri enhancer complains that
it can't find org/apache/jdo/tck/util/DeepEquality.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Commented] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13234066#comment-13234066
]
Michelle Caisse commented on JDO-706:
-
log4j: Trying to find [log4j.xml] using context classloader
org.codehaus.classworlds.RealmClassLoader@143d2a58.
log4j: Trying to find [log4j.xml] using
org.codehaus.classworlds.RealmClassLoader@143d2a58 class loader.
log4j: Trying to find [log4j.xml] using ClassLoader.getSystemResource().
log4j: Trying to find [log4j.properties] using context classloader
org.codehaus.classworlds.RealmClassLoader@143d2a58.
log4j: Trying to find [log4j.properties] using
org.codehaus.classworlds.RealmClassLoader@143d2a58 class loader.
log4j: Trying to find [log4j.properties] using ClassLoader.getSystemResource().
log4j: Could not find resource: [null].
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Commented] (JDO-706) No enhancer log output with maven 2
[
https://issues.apache.org/jira/browse/JDO-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13233168#comment-13233168
]
Michelle Caisse commented on JDO-706:
-
The approach suggested to solving this problem is to manually add the log4j jar
file to the class loader used to invoke JdoHelper.getEnhancer(ClassLoader) and
to remove it from the project dependencies, so that log4j.properties file will
be found in the root directory of the class loader used to load log4j. I have
been able to make this approach work in a test environment; however, it entails
removing springframework from the dependencies as well, since it has log4j as a
transitive dependency. (To verify this, run mvn -X jdo-exectck:enhance.) I need
input on how to proceed.
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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
Re: Minutes: JDO TCK Conference Call Friday, Mar 9, 9 am Pacific Time
On 3/9/2012 11:18 AM, Craig L Russell wrote: Attendees: Michelle Caisse, Michael Bouschen, Craig Russell Agenda: 1. README.html under trunk needs to be reviewed. AI Everyone please READ ME. 2. log4j class loader, no enhancer log output with maven 2: https://issues.apache.org/jira/browse/JDO-706? AI Michelle try some more experiments with the iut and jdori profiles. Specifying -P iut on command line should work, disable the jdori profile. Exectck should be able to ask maven which profile(s) are active. This page seems to indicate that there is no programmatic way of determining which profile is active. It suggests using an environment variable, as I've done in exectck. http://maven.40175.n5.nabble.com/get-active-profile-in-pom-td108838.html This page documents that an activeByDefault profile will deactivate when another profile is activated /by any available means. /http://maven.apache.org/guides/introduction/introduction-to-profiles.html: Profiles can also be active by default using a configuration like the following: profiles profile idprofile-1/id activation activeByDefaulttrue/activeByDefault /activation ... /profile /profiles This profile will automatically be active for all builds/unless another profile in the same POM is activated using one of the previously described methods. All profiles that are active by default are automatically deactivated when a profile in the POM is activated on the command line or through its activation config./ [My italics.] Thus my setup in exectck pom.xml should work fine. -- Michelle 3. Refactor JDO parent child poms https://issues.apache.org/jira/browse/JDO-707 It's not obvious why a parent pom at the same level as others is better than the current pom in the trunk directory. 4. Create JIRA component entry for exectck parent-pom modules https://issues.apache.org/jira/browse/JDO-708 It's not obvious that exectck and tck are different components even thought they are physically different. 5. Issue with setting autoCreateTables=false The sequence support for Derby is now included in DataNucleus. But it doesn't seem to work. Change the mapping in the orm file to include the schema name. But is this the only way for DN to find the sequence? Maybe need to add schema to the package entry in the orm. 6. What's needed to release 3.1? Go to https://issues.apache.org/jira/secure/BrowseProject.jspa?id=10630, click Issues in the menu on the left and then click JDO 3 maintenacnce release 1 (3.1) under Unresolved: By Version Still waiting for log4j class loader, sequences, and specification updates. 7. Other issues 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 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-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13226250#comment-13226250 ] Michelle Caisse commented on JDO-708: - Wondering what the benefit is of this change over the existing setup? 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 Components: site and infrastructure 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] [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=13226253#comment-13226253 ] Michelle Caisse commented on JDO-707: - Wondering what the benefit is of this change over the existing setup? 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] [Updated] (JDO-708) Create JIRA component entry for exectck parent-pom modules
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse updated JDO-708: Comment: was deleted (was: Wondering what the benefit is of this change over the existing setup?) 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 Components: site and infrastructure 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
Re: log4j class loader
We already have resource paths set up in the tck project that include
src/conf, which contains log4j.properties. I tried adding the same
lines to exectck, but still get the log4j warning. I looked at the
jdo-tck-3.1-SNAPSHOT.jar file and both log4j-1.2.13.jar and
log4j.properties are in the jar at the root level.
-- Michelle
On 3/7/2012 8:16 PM, Craig L Russell wrote:
Hi Michelle,
I think this problem is due to the maven setup.
If you have maven set up your classpath, and declare a dependency on
log4j, then maven will put the log4j.jar file into the classpath.
But in order to have maven also put log4j.properties into the
classpath, you need tell maven to add a dependency on a resources
directory that has the log4j.properties.
For example,
build
resources
resource
directorysrc/main/resources/directory
/resource
/resources
What the above snippet does is to add src/main/resources to the
classpath when building the jar file. Something similar needs to be
done for exectck or tck...
Craig
On Mar 7, 2012, at 6:28 PM, Michelle Caisse wrote:
Which classloader is the one used to load log4j? -- Michelle
On 3/6/2012 7:36 PM, Craig L Russell wrote:
Hi Michelle,
On Mar 6, 2012, at 5:50 PM, Michelle Caisse wrote:
On 3/2/2012 11:25 AM, Craig L Russell wrote:
It looks like log4j looks in the class loader that loads the log4j
classes [1], so putting the configuration file directory in the
class loader used to load log4j should work.
Would it then also be the case that putting the configuration file
in the directory from which the log4j jar file is loaded should
work? I tried this and it did not work.
I looked in Enhance.java and couldn't quite figure out where the
log4j jar file is being added to the class path.
Log4j is handled by maven's dependency management. The same is
currently true for the DataNucleus jars, though I had worked on an
alternative to remove DataNucleus from the classpath when the IUT
was run.
If you're using maven for dependency management, then maven is only
going to add the log4j.jar to the classpath, not the directory in
which log4j.jar is located.
I'd suggest *not* using maven for dependencies for jdori, as it
makes jdori not like iut.
How about creating a directory for the known jdori dependencies
including the log4j.properties and all of DN dependencies and
treating it just like an iut except that it's configured by exectck.
Then as soon as jdori works, we can expect that a properly set up
iut will also work.
I understand that there is then a bit of duplicate work to configure
jdori if you use mvn dependency management for DN, but I think
removing DN and its dependencies from mvn management is actually a
good thing.
Craig
-- Michelle
URL[] classPathURLs = new URL[2];
ArrayListURL cpList = new ArrayListURL();
ClassLoader loader = null;
try {
cpList.add((new
File(enhancedIdDirName)).toURI().toURL());
cpList.add((new File(fromDirName)).toURI().toURL());
String[] jars = {jar};
if (impl.equals(iut)) {
fi = FileUtils.iterateFiles(new
File(iutLibsDirectory), jars, true);
while (fi.hasNext()) {
cpList.add(fi.next().toURI().toURL());
}
}
loader = new
URLClassLoader(cpList.toArray(classPathURLs),
getClass().getClassLoader());
// Utilities.printClasspath(loader);
} catch (MalformedURLException ex) {
Logger.getLogger(Enhance.class.getName()).log(Level.SEVERE, null,
ex);
}
Actually, I can't figure out where DataNucleus and log4j are being
added to the class path of the loader.
Craig
[1] sources from log4j
/**
69
This method will search for coderesource/code in different
70
places. The search order is as follows:
71
72
ol
73
74
pliSearch for coderesource/code using the thread context
75
class loader under Java2. If that fails, search for
76
coderesource/code using the class loader that loaded this
77
class (codeLoader/code). Under JDK 1.1, only the the class
78
loader that loaded this class (codeLoader/code) is used.
79
80
pliTry one last time with
81
codeClassLoader.getSystemResource(resource)/code, that is is
82
using the system class loader in JDK 1.2 and virtual machine's
83
built-in class loader in JDK 1.1.
84
85
/ol
86
*/
87
static public URL getResource(String resource) {
88
ClassLoader classLoader = null;
89
URL url = null;
90
91
try {
92
if(!java1 !ignoreTCL) {
93
classLoader = getTCL();
94
if(classLoader != null) {
95
LogLog.debug(Trying to find [+resource+] using context
classloader
96
+classLoader+.);
97
url = classLoader.getResource(resource);
98
if(url != null) {
99
return url;
100
}
101
}
102
}
103
104
// We could not find resource. Ler us now try with the
105
// classloader that loaded this class.
106
classLoader = Loader.class.getClassLoader
Re: log4j class loader
On 3/2/2012 11:25 AM, Craig L Russell wrote:
It looks like log4j looks in the class loader that loads the log4j
classes [1], so putting the configuration file directory in the class
loader used to load log4j should work.
Would it then also be the case that putting the configuration file in
the directory from which the log4j jar file is loaded should work? I
tried this and it did not work.
I looked in Enhance.java and couldn't quite figure out where the log4j
jar file is being added to the class path.
Log4j is handled by maven's dependency management. The same is currently
true for the DataNucleus jars, though I had worked on an alternative to
remove DataNucleus from the classpath when the IUT was run.
-- Michelle
URL[] classPathURLs = new URL[2];
ArrayListURL cpList = new ArrayListURL();
ClassLoader loader = null;
try {
cpList.add((new
File(enhancedIdDirName)).toURI().toURL());
cpList.add((new File(fromDirName)).toURI().toURL());
String[] jars = {jar};
if (impl.equals(iut)) {
fi = FileUtils.iterateFiles(new
File(iutLibsDirectory), jars, true);
while (fi.hasNext()) {
cpList.add(fi.next().toURI().toURL());
}
}
loader = new
URLClassLoader(cpList.toArray(classPathURLs),
getClass().getClassLoader());
// Utilities.printClasspath(loader);
} catch (MalformedURLException ex) {
Logger.getLogger(Enhance.class.getName()).log(Level.SEVERE, null, ex);
}
Actually, I can't figure out where DataNucleus and log4j are being
added to the class path of the loader.
Craig
[1] sources from log4j
/**
69
This method will search for coderesource/code in different
70
places. The search order is as follows:
71
72
ol
73
74
pliSearch for coderesource/code using the thread context
75
class loader under Java2. If that fails, search for
76
coderesource/code using the class loader that loaded this
77
class (codeLoader/code). Under JDK 1.1, only the the class
78
loader that loaded this class (codeLoader/code) is used.
79
80
pliTry one last time with
81
codeClassLoader.getSystemResource(resource)/code, that is is
82
using the system class loader in JDK 1.2 and virtual machine's
83
built-in class loader in JDK 1.1.
84
85
/ol
86
*/
87
static public URL getResource(String resource) {
88
ClassLoader classLoader = null;
89
URL url = null;
90
91
try {
92
if(!java1 !ignoreTCL) {
93
classLoader = getTCL();
94
if(classLoader != null) {
95
LogLog.debug(Trying to find [+resource+] using context classloader
96
+classLoader+.);
97
url = classLoader.getResource(resource);
98
if(url != null) {
99
return url;
100
}
101
}
102
}
103
104
// We could not find resource. Ler us now try with the
105
// classloader that loaded this class.
106
classLoader = Loader.class.getClassLoader();
107
if(classLoader != null) {
108
LogLog.debug(Trying to find [+resource+] using +classLoader
109
+ class loader.);
110
url = classLoader.getResource(resource);
111
if(url != null) {
112
return url;
113
}
114
}
115
} catch(IllegalAccessException t) {
116
LogLog.warn(TSTR, t);
117
} catch(InvocationTargetException t) {
118
if (t.getTargetException() instanceof InterruptedException
119
|| t.getTargetException() instanceof InterruptedIOException) {
120
Thread.currentThread().interrupt();
121
}
122
LogLog.warn(TSTR, t);
123
} catch(Throwable t) {
124
//
125
// can't be InterruptedException or InterruptedIOException
126
// since not declared, must be error or RuntimeError.
127
LogLog.warn(TSTR, t);
128
}
129
130
// Last ditch attempt: get the resource from the class path. It
131
// may be the case that clazz was loaded by the Extentsion class
132
// loader which the parent of the system class loader. Hence the
133
// code below.
134
LogLog.debug(Trying to find [+resource+
135
] using ClassLoader.getSystemResource().);
136
return ClassLoader.getSystemResource(resource);
137
}
138
13
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] [Created] (JDO-706) No enhancer log output with maven 2
No enhancer log output with maven 2
---
Key: JDO-706
URL: https://issues.apache.org/jira/browse/JDO-706
Project: JDO
Issue Type: Bug
Components: tck
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Assignee: Michelle Caisse
No log output for enhancement is produced. The following warnings are issued:
[INFO] [jdo-exectck:enhance {execution: default-cli}]
log4j:WARN No appenders could be found for logger (DataNucleus.Enhancer).
log4j:WARN Please initialize the log4j system properly.
Enhancing classes for identity type datastoreidentity
The classpath available to the enhancer does not provide access to the log
properties 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] [Resolved] (JDO-647) Run TCK using Maven2 for consistency
[ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Caisse resolved JDO-647. - Resolution: Fixed Opened issue 706 to track the remaining problem with enhancer log output. Run TCK using Maven2 for consistency Key: JDO-647 URL: https://issues.apache.org/jira/browse/JDO-647 Project: JDO Issue Type: Improvement Components: tck Affects Versions: JDO 3 (3.0) Reporter: Andy Jefferson Assignee: Michelle Caisse Fix For: JDO 3 maintenance release 1 (3.1) Attachments: JDO-647-default-cfgList.patch, JDO-647-impl-log.patch, JDO-647-pom-properties.zip, JDO-647-rootPomChanges.patch, RunRules.patch, api_pom.diff, exectck.zip, exectck.zip, pom.xml, pom.xml Since api2 now builds using Maven2 it makes a heck of a lot of sense to build/run the TCK using that too. It also means that the DataNucleus M1 repo (which only exists for use of this TCK) can be deleted. Please consider upgrading to Maven2 -- 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
Re: Minutes: JDO TCK Conference Call Friday, Feb 17, 9 am Pacific Time
Done. -- Michelle 5. Everyone please review the ChangeLog: http://wiki.apache.org/jdo/ChangeLog Good feedback on the change log. Thanks, Andy. Items on the PROPOSED list that are already in 3.0. AI Michelle move 12, 13, 14, 15, 16, 17 to ACCEPTED, and move ACCEPTED 7 to the same block of changes.
[jira] [Created] (JDO-704) API test compilation failure
API test compilation failure
Key: JDO-704
URL: https://issues.apache.org/jira/browse/JDO-704
Project: JDO
Issue Type: Bug
Components: api
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Michelle Caisse
Fix For: JDO 3 maintenance release 1 (3.1)
On building API:
Compiling 33 source files to C:\jdo_newest\api\target\test-classes
[ERROR]BUILD FAILURE
Compilation failure
javax/jdo/stub/StubPMF.java:[554,9] method does not override a method from its
superclass
The problem appears to be that this method does not return a value:
public CollectionClass getManagedClasses() {
throw new UnsupportedOperationException(not implemented);
}
--
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
JDO TCK Conference Call Friday, Dec 2, 9 am Pacific Time
Hi, We will have our regular meeting Friday, December 2 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. JDO 3.0.1 release status 2. News on new feature idea http://osdir.com/ml/jdo-dev-db-apache/2011-11/msg2.html - possible code contribution from 3M 3. Case-insensitive properties, patch ready to be checked in? See https://issues.apache.org/jira/browse/JDO-696 4. Support for specification of embedded inherited objects, see https://issues.apache.org/jira/browse/JDO-702 5. Other issues 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 document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
JDO TCK Conference Call Friday,Nov 3, 9 am Pacific Time [TIME CHANGE IN SOME REGIONS]
Hi, We will have our regular meeting Friday, November 3 at 9 am Pacific Time to discuss JDO TCK issues and status. * The US goes off of daylight savings time NEXT week. In those regions that have already gone off of daylight savings time, the meeting will be ONE HOUR EARLIER than normal this week. * Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. JDO 3.0.1 release is available for testing! 2. New feature idea http://osdir.com/ml/jdo-dev-db-apache/2011-11/msg2.html 3. Other issues 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.
JDO TCK Conference Call Friday, Oct 28, 9 am Pacific Time
Hi, We will have our regular meeting Friday, October 28 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. JDO 3.0.1 release issues 2. Spec updates for JDOQL : Support for further methods (String, Enum, Date, JDOHelper) https://issues.apache.org/jira/browse/JDO-658 3. Other issues 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.
JDO TCK Conference Call Friday, Oct 21, 9 am Pacific Time
Hi, We will have our regular meeting Friday, October 21 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. JDO 3.0.1 release - any followup required 2. Review recently added JIRA issues 3. Other issues 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.
JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
Hi, We will have our regular meeting Friday, October 14 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. Fix OSGi Export-Package entries https://issues.apache.org/jira/browse/JDO-684 2. JDO 3.0 dependency on JPA 3. Other issues 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.
JDO TCK Conference Call Friday, Oct 7, 9 am Pacific Time
Hi, We will have our regular meeting Friday, October 7 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. 3.0.1 patch (see https://issues.apache.org/jira/browse/JDO/fixforversion/12317950) 2. New JIRAs: https://issues.apache.org/jira/browse/JDO-688 https://issues.apache.org/jira/browse/JDO-695 3. Other issues 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.
