[jira] Commented: (DERBY-3804) Provide localizations for messages added in 10.4.
[ https://issues.apache.org/jira/browse/DERBY-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12618467#action_12618467 ] Jean T. Anderson commented on DERBY-3804: - Rick, who is actually producing and contributing these translations? I kind of doubt that you're bilingual in *all* these languages, but if you are, my hat's off to you! mostly I'd like to avoid any perception of commit by proxy, which Apache doesn't do -- but there *are* ways to contribute work produced by others. Provide localizations for messages added in 10.4. - Key: DERBY-3804 URL: https://issues.apache.org/jira/browse/DERBY-3804 Project: Derby Issue Type: Improvement Components: Localization Affects Versions: 10.4.1.4, 10.5.0.0 Reporter: Rick Hillegas Assignee: Rick Hillegas Attachments: changes.html, derby-3804-01-aa-stage1.diff, derby-3804-02-aa-stage2.diff, vetStage1.tar Provide translations to certain languages for messages added in 10.4. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3804) Provide localizations for messages added in 10.4.
[ https://issues.apache.org/jira/browse/DERBY-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12618499#action_12618499 ] Jean T. Anderson commented on DERBY-3804: - IBM sent Apache a software grant that included the message files. Did Sun every send a software grant to Apache covering those files? I don't know if a new software grant is required for each update to those files -- that's probably something we should ask legal-discuss to make sure everything is in order. Provide localizations for messages added in 10.4. - Key: DERBY-3804 URL: https://issues.apache.org/jira/browse/DERBY-3804 Project: Derby Issue Type: Improvement Components: Localization Affects Versions: 10.4.1.4, 10.5.0.0 Reporter: Rick Hillegas Assignee: Rick Hillegas Attachments: changes.html, derby-3804-01-aa-stage1.diff, derby-3804-02-aa-stage2.diff, vetStage1.tar Provide translations to certain languages for messages added in 10.4. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3444) Tearoff database demo
[ https://issues.apache.org/jira/browse/DERBY-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571459#action_12571459 ] Jean T. Anderson commented on DERBY-3444: - Another thing that troubles me about putting big application demos into the code base is derby-dev had a vigorous discussion in june 2006 about adding user applications to the wiki. See the thread starting at [1]. Users sharing code on the derby wiki was pretty much shot down. I just took a quick look at the Hibernate wiki page on the Derby wiki [2] and noticed a link to a code wad stored at sourceforge: Scripts Fundraising Manager . That was just the wiki. If we now add a precedent for adding applications to the derby code line, what criteria do we use for including/excluding a potential contribution? [1] http://mail-archives.apache.org/mod_mbox/db-derby-dev/200606.mbox/[EMAIL PROTECTED] [2] http://wiki.apache.org/db-derby/HibernateHelp Tearoff database demo - Key: DERBY-3444 URL: https://issues.apache.org/jira/browse/DERBY-3444 Project: Derby Issue Type: Task Components: Demos/Scripts Affects Versions: 10.4.0.0 Reporter: Rick Hillegas Attachments: derby-3444-01-initial.diff Create a demonstration of tearoff databases. This shows how to use arbitrary, parameterized queries to tearoff datasets from an arbitrary server-hosted database and load those datasets into a Derby database running on a handset. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3444) Tearoff database demo
[ https://issues.apache.org/jira/browse/DERBY-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571479#action_12571479 ] Jean T. Anderson commented on DERBY-3444: - Being focused in specific areas is great -- and I'm all for that. Good things happen that way. But I'm opposed to forming a policy that excludes the community at large. We sent a message in june 2006 that the derby project is not the place to host user applications. If we want to revisit the closed policy, great. But let's open it up to everyone in the derby community. A sandbox might be an option [1]. [1] http://mail-archives.apache.org/mod_mbox/db-derby-dev/200606.mbox/[EMAIL PROTECTED] Tearoff database demo - Key: DERBY-3444 URL: https://issues.apache.org/jira/browse/DERBY-3444 Project: Derby Issue Type: Task Components: Demos/Scripts Affects Versions: 10.4.0.0 Reporter: Rick Hillegas Attachments: derby-3444-01-initial.diff Create a demonstration of tearoff databases. This shows how to use arbitrary, parameterized queries to tearoff datasets from an arbitrary server-hosted database and load those datasets into a Derby database running on a handset. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3444) Tearoff database demo
[ https://issues.apache.org/jira/browse/DERBY-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12571199#action_12571199 ] Jean T. Anderson commented on DERBY-3444: - Rick, could you confirm that you produced this code as part of the presentation Dan referenced at http://download.java.net/mobileembedded/developerdays/2008/TS-7-tearoffToHandset-final.pdf ? Do we want to be adding presentation demos to the code base itself? We actually do have some demos that folks have contributed, but they are hosted on the web site [1] not in the code base itself, and nothing is anywhere near this big. We've pointed to external resources from the ApacheCon page on the derby site[2] , but we certainly aren't restricted to just ApacheCon-related activities. There's also a Miscellaneous Derby Presentations page [3] that hasn't been used much -- I wonder if that might be an option in this case. [1] http://db.apache.org/derby/integrate/index.html [2] http://db.apache.org/derby/papers/ApacheCon.html [3] http://db.apache.org/derby/papers/MiscPresentations.html Tearoff database demo - Key: DERBY-3444 URL: https://issues.apache.org/jira/browse/DERBY-3444 Project: Derby Issue Type: Task Components: Demos/Scripts Affects Versions: 10.4.0.0 Reporter: Rick Hillegas Attachments: derby-3444-01-initial.diff Create a demonstration of tearoff databases. This shows how to use arbitrary, parameterized queries to tearoff datasets from an arbitrary server-hosted database and load those datasets into a Derby database running on a handset. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3264) track changes for 10.3.2.1 release
[ https://issues.apache.org/jira/browse/DERBY-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549627 ] Jean T. Anderson commented on DERBY-3264: - From a structural viewpoint, the cgi file looks fine to me. I appreciate that not being able to test the cgi before deploying it on people.a.o can be unnerving. For other extreme web site changes I have sometime copied build/site to a temp location locally, removed all the files from build/site/binaries (to make the result smaller), then tar'd it up and scp'd it to my public_html directory on people.a.o. So, if you want that extra measure of security in this case, you might consider it. But if the deployment goofs up, don't lose any sleep over it. there's plenty of opportunity to correct it. In the meantime, people can always get to the latest archive release. track changes for 10.3.2.1 release --- Key: DERBY-3264 URL: https://issues.apache.org/jira/browse/DERBY-3264 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.3.2.1 Reporter: Kathey Marsden Assignee: Kathey Marsden Priority: Minor Attachments: derby_3264_web_diff.txt Track changes for 10.3.2.1 release. I probably should have created this earlier, but making it now that I can post website patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-232) Open Invitation to add a Question and Answer to Derby FAQs
[ https://issues.apache.org/jira/browse/DERBY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531356 ] Jean T. Anderson commented on DERBY-232: Committed John's Sep 6 suggestion in rev 580757 (thanks, John!). Open Invitation to add a Question and Answer to Derby FAQs -- Key: DERBY-232 URL: https://issues.apache.org/jira/browse/DERBY-232 Project: Derby Issue Type: Task Components: Web Site Reporter: Jean T. Anderson Assignee: Jean T. Anderson Priority: Trivial Add a comment to this Jira issue with the FAQ entry (both the question and the answer) you would like to be added to http://db.apache.org/derby/faq.html, and the assignee will add it. Indicate in your comment if the FAQ belongs in the Developing Derby or Using Derby section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-232) Open Invitation to add a Question and Answer to Derby FAQs
[ https://issues.apache.org/jira/browse/DERBY-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-232: --- Description: Add a comment to this Jira issue with the FAQ entry (both the question and the answer) you would like to be added to http://db.apache.org/derby/faq.html, and the assignee will add it. Setting the Patch Available flag is a great way to keep a new FAQ on the radar until committed, even if the text of the FAQ is in a comment instead of in an actual patch. Indicate in your comment if the FAQ belongs in the Developing Derby or Using Derby section. was: Add a comment to this Jira issue with the FAQ entry (both the question and the answer) you would like to be added to http://db.apache.org/derby/faq.html, and the assignee will add it. Indicate in your comment if the FAQ belongs in the Developing Derby or Using Derby section. Derby Info: (was: [Patch Available]) Open Invitation to add a Question and Answer to Derby FAQs -- Key: DERBY-232 URL: https://issues.apache.org/jira/browse/DERBY-232 Project: Derby Issue Type: Task Components: Web Site Reporter: Jean T. Anderson Assignee: Jean T. Anderson Priority: Trivial Add a comment to this Jira issue with the FAQ entry (both the question and the answer) you would like to be added to http://db.apache.org/derby/faq.html, and the assignee will add it. Setting the Patch Available flag is a great way to keep a new FAQ on the radar until committed, even if the text of the FAQ is in a comment instead of in an actual patch. Indicate in your comment if the FAQ belongs in the Developing Derby or Using Derby section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2924) Manual copyright topics need to be updated to current year
[ https://issues.apache.org/jira/browse/DERBY-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512108 ] Jean T. Anderson commented on DERBY-2924: - I believe 2004, 2006 and 2004- 2006 are the same, both indicating a range of years starting with that first date. More info is at: http://www.apache.org/dev/apply-license.html#new Manual copyright topics need to be updated to current year -- Key: DERBY-2924 URL: https://issues.apache.org/jira/browse/DERBY-2924 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.3.0.0 Reporter: Kim Haase Assignee: Kim Haase Priority: Blocker Attachments: DERBY-2924-2.diff, DERBY-2924.diff Although the ditamap files of all the manuals have been updated with the tag copyryear year=2004, 2007/, the copyright topics all contain the dates 2004, 2006. adminguide/radmincopyright.dita:Derby/alt/image/p pCopyright 2004, 2006 The Apache Software Foundation/p p Licensed devguide/rdevcopyright.dita:Derby/alt/image/p pCopyright 2004, 2006 The Apache Software Foundation/p p Licensed getstart/rgscopyright.dita:Derby/alt/image/p pCopyright 2004, 2006 The Apache Software Foundation/p p Licensed ref/rrefcopyright.dita:Derby/alt/image/p pCopyright 2004, 2006 The Apache Software Foundation/p p Licensed tools/rtoolscopyright.dita:Derby/alt/image/p pCopyright 2004, 2006 The Apache Software Foundation/p p Licensed tuning/rtuncopyright.dita:Derby/alt/image/p pCopyright 2004, 2006 The Apache Software Foundation/p p Licensed I would appreciate some feedback on how urgent it is to fix this for the 10.3 release. I'm sorry not to have noticed it before. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1377) Update copyright headers to comply with new ASF policy
[ https://issues.apache.org/jira/browse/DERBY-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505283 ] Jean T. Anderson commented on DERBY-1377: - Myrna asked: Do we need to do a similar exercise for the 10.2 branch or can we wait until someone chooses to make a release? Wait until there is a release need. We should add a Check source headers item to http://wiki.apache.org/db-derby/DerbySnapshotOrRelease if it isn't there already. thanks for taking care of this, Myrna! Update copyright headers to comply with new ASF policy -- Key: DERBY-1377 URL: https://issues.apache.org/jira/browse/DERBY-1377 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.2.0 Reporter: Jean T. Anderson Assignee: Myrna van Lunteren Fix For: 10.3.0.0 Attachments: derby-1377-v01.diff, derby-1377-v01.status, derby-1377-v02-nist.diff, derby-1377-v02-nist.status, DERBY-1377_NOTICE_diff.txt, engineOrgApacheDerbyIapiError.zip, engineOrgApacheDerbyIapiReference.zip, engineOrgApacheDerbyIapiSql.zip, engineOrgApacheDerbyIapiUtil.zip, engineOrgApacheDerbyImplLoad.zip, engineOrgApacheDerbyImplSql.zip, fixsqlheaders.ksh, ij_header, license_header, testingOrgApacheDerbyTestingFunctionTestsTestsLang.diff, testingOrgApacheDerbyTestingFunctionTestsTestsLang.diff, testingOrgApacheDerbyTestingFunctionTestsTestsLang.stat, testingOrgApacheDerbyTestingFunctionTestsTestsLang.stat A new copyright header policy will take effect for distributions released starting on Sep 1, 2006. Committers will receive notification, but a heads up with details is in the legal-discuss thread starting with http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200606.mbox/[EMAIL PROTECTED] Date was 1-Aug-2006, is now 1-Sep-2006: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200607.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2461) Convert lang/procedure.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2461: Attachment: derby-2461-pre.diff I need to focus attention elsewhere for a while, so can't work on converting this test right now and will unassign myself. I attached a patch with how far I got so far just in case somebody else is interested in picking it up. You're welcome to use it as a starting point (or toss it and start over). If nobody has picked it up by the time I can focus time on it again, I'll pick it back up. The patch sets up the JUnit framework and converts just the first two tests in lang/procedure.java: testNegative and testDelayedClassChecking, and it splits testNegative, which I thought was kind of long, into two methods: testCreateRoutineErrors testMethodSignatureDerby258 testCreateRoutineErrors still uses the old statementExceptionExpected() method from procedure.java, but with arguments swapped around to match assertStatementError. It should be able to use the BaseJDBCTestCase assertStatementError method (testMethodSignatureDerby258 uses it just fine, as does the XMLTypeAndOpsTest suite). The cause is probably staring me right in the face and I'm not seeing it. Convert lang/procedure.java to junit Key: DERBY-2461 URL: https://issues.apache.org/jira/browse/DERBY-2461 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2461-pre.diff Convert the lang/procedure.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2461) Convert lang/procedure.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson reassigned DERBY-2461: --- Assignee: (was: Jean T. Anderson) Convert lang/procedure.java to junit Key: DERBY-2461 URL: https://issues.apache.org/jira/browse/DERBY-2461 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Priority: Minor Attachments: derby-2461-pre.diff Convert the lang/procedure.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2458: Derby Info: (was: [Patch Available]) One step that remains is to delete the old test. A checklist is at http://wiki.apache.org/db-derby/ConvertOldTestToJunitTips#DeleteOldHarnessFiles Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458__stat_03_20.txt, DERBY-2458_diff_03_16.txt, DERBY-2458_diff_03_16_ver2.txt, DERBY-2458_diff_03_19.txt, DERBY-2458_diff_03_20.txt, DERBY-2458_diff_03_20_ver2.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_03_19.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482948 ] Jean T. Anderson commented on DERBY-2458: - Committed patch DERBY-2458_diff_03_21.txt, revision 521036 with one additional change that removed unaryArithmeticDynamicParameter.java from suites/derbynetmats.runall. Thanks, Manjula! Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458__stat_03_20.txt, DERBY-2458_diff_03_16.txt, DERBY-2458_diff_03_16_ver2.txt, DERBY-2458_diff_03_19.txt, DERBY-2458_diff_03_20.txt, DERBY-2458_diff_03_20_ver2.txt, DERBY-2458_diff_03_21.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_03_19.txt, DERBY-2458_stat_03_21.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482424 ] Jean T. Anderson commented on DERBY-2458: - So I'm a little confused by the Patch generally looks good but it's good to have clear logical naming. Is this patch ready to commit? If so, I'll go ahead and do so, Or do you want the naming changed first? Would it be sufficient for me to change the JDBC.assertColumnTypes to JDBC.assertParameterTypes when it's committed? Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458_diff_03_16.txt, DERBY-2458_diff_03_16_ver2.txt, DERBY-2458_diff_03_19.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_03_19.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482454 ] Jean T. Anderson commented on DERBY-2458: - Actually, I can't apply the latest patch (DERBY-2458_diff_03_19.txt), I get this error: patching file java/testing/org/apache/derbyTesting/functionTests/tests/lang/_Suite.java patch: malformed patch at line 377: Index: java/testing/org/apache/derbyTesting/junit/JDBC.java I'm not spotting what the problem is in the patch file. Manjula, I suggest that you sync up to the latest svn revision, take care of the remaining comments, and upload a final patch. Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458_diff_03_16.txt, DERBY-2458_diff_03_16_ver2.txt, DERBY-2458_diff_03_19.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_03_19.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482527 ] Jean T. Anderson commented on DERBY-2458: - Almost there ... unfortunately DERBY-2458_diff_03_20.txt gets a Hunk failure at 77 -- the problem is with _Suite.java. Please be sure to do an 'svn up'. For a tricky patch, especially if your svn working copy has a lot going on and your patch applies to just some of those changes, it might make sense to do a fresh checkout and apply your patch there to make sure it will work. Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458__stat_03_20.txt, DERBY-2458_diff_03_16.txt, DERBY-2458_diff_03_16_ver2.txt, DERBY-2458_diff_03_19.txt, DERBY-2458_diff_03_20.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_03_19.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2275) XSLT changes for PDF output
[ https://issues.apache.org/jira/browse/DERBY-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson closed DERBY-2275. --- XSLT changes for PDF output --- Key: DERBY-2275 URL: https://issues.apache.org/jira/browse/DERBY-2275 Project: Derby Issue Type: Improvement Components: Documentation Environment: any Reporter: scott hutinger Priority: Minor Fix For: 10.3.0.0 Attachments: header1.patch.gz, header2.patch.gz patch for dita2fo-shell.xsl - adds copyright to title page - header is now the document title instead of Copyright - Table of contents header has derby version and name of document on the header -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson closed DERBY-2428. --- Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1324) Need to remove old copyright notice
[ https://issues.apache.org/jira/browse/DERBY-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson closed DERBY-1324. --- Need to remove old copyright notice --- Key: DERBY-1324 URL: https://issues.apache.org/jira/browse/DERBY-1324 Project: Derby Issue Type: Bug Components: Tools Affects Versions: 10.1.2.1 Reporter: Jean T. Anderson Assigned To: Andrew McIntyre Fix For: 10.0.2.2, 10.1.3.1, 10.2.1.6 Attachments: derby-1324.diff An IBM copyright is in these files: derby/code/trunk/tools/jar/copyright.txt derby/code/branches/10.1/tools/jar/copyright.txt derby/code/branches/10.0/tools/jar/copyright.txt 'svn log' shows it was part of the original code contribution -- I think this was just missed in the copyright cleanup. There also exists reference to CPL in java\drda\org\apache\derby\impl\drda\EbcdicCcsidManager.java(22): http://www.ibm.com/developerworks/oss/CPLv1.0.htm More references: java\engine\org\apache\derby\database\Database.java(47): * IIBM Corp. reserves the right to change, rename, or java\engine\org\apache\derby\database\UserUtility.java(41): IBM Corp. reserves the right java\engine\org\apache\derby\iapi\db\ConnectionInfo.java(40): * iIBM Corp. reserves the right to change, rename or remove this class or java\engine\org\apache\derby\iapi\db\ConsistencyChecker.java(70): * IIBM Corp. reserves the right to change, rename, or java\engine\org\apache\derby\iapi\db\Factory.java(58): * IIBM Corp. reserves the right to change, rename, or java\engine\org\apache\derby\iapi\db\PropertyInfo.java(54): * IIBM Corp. reserves the right to change, rename, or java\engine\org\apache\derby\iapi\db\TriggerExecutionContext.java(32): * IIBM Corp. reserves the right to change, rename, or java\engine\org\apache\derby\impl\sql\compile\AggregateDefinition.java(46): * I IBM Corp. reserves the right to change, rename, or java\engine\org\apache\derby\vti\VTICosting.java(40): * IIBM Corp reserves the right to change, rename, or java\engine\org\apache\derby\vti\VTIEnvironment.java(29): * IIBM Corp. reserves the right to change, rename, or -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-1377) Update copyright headers to comply with new ASF policy
[ https://issues.apache.org/jira/browse/DERBY-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson closed DERBY-1377. --- I don't see any outstanding items, so am closing. Update copyright headers to comply with new ASF policy -- Key: DERBY-1377 URL: https://issues.apache.org/jira/browse/DERBY-1377 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.2.0 Reporter: Jean T. Anderson Assigned To: Rick Hillegas Fix For: 10.2.2.0 Attachments: derby-1377-v01.diff, derby-1377-v01.status, derby-1377-v02-nist.diff, derby-1377-v02-nist.status, DERBY-1377_NOTICE_diff.txt, engineOrgApacheDerbyIapiError.zip, engineOrgApacheDerbyIapiReference.zip, engineOrgApacheDerbyIapiSql.zip, engineOrgApacheDerbyIapiUtil.zip, engineOrgApacheDerbyImplLoad.zip, engineOrgApacheDerbyImplSql.zip, fixsqlheaders.ksh, ij_header, license_header, testingOrgApacheDerbyTestingFunctionTestsTestsLang.diff, testingOrgApacheDerbyTestingFunctionTestsTestsLang.diff, testingOrgApacheDerbyTestingFunctionTestsTestsLang.stat, testingOrgApacheDerbyTestingFunctionTestsTestsLang.stat A new copyright header policy will take effect for distributions released starting on Sep 1, 2006. Committers will receive notification, but a heads up with details is in the legal-discuss thread starting with http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200606.mbox/[EMAIL PROTECTED] Date was 1-Aug-2006, is now 1-Sep-2006: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200607.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2398: Derby Info: (was: [Patch Available]) Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, patch-2398.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482633 ] Jean T. Anderson commented on DERBY-2458: - Committed patch DERBY-2458_diff_03_20_ver2.txt, revision 520709. Thanks, Manjula! Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458__stat_03_20.txt, DERBY-2458_diff_03_16.txt, DERBY-2458_diff_03_16_ver2.txt, DERBY-2458_diff_03_19.txt, DERBY-2458_diff_03_20.txt, DERBY-2458_diff_03_20_ver2.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_03_19.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482162 ] Jean T. Anderson commented on DERBY-2398: - Regarding the j9 question, Myrna posted this comment to derby-dev [1]: Just jumping in on this part - we don't need to worry about j9 per se. That was created for IBM's jclMax implementation with wctme5.7, but it was based on jdk 1.3, which we no longer support with our 10.3 codeline. j9_foundation is (with 10.3) changed to mean weme6.1's implementation, which is J2ME 1.1 / JSR169; that we still worry about and it can be addressed by checking JDBC.vmSupportsJSR169. JDBC.vmSupportsJdbc20() will return false for that JVM, as (I think) will vmSupportsJdbc30(). I didn't see any response to the question if getGeneratedKeys() should return a NULL key after commit/rollback.[2] If there's no comment regarding the observation that testResultSetGarbageCollection() is slow (or any other objections raised), I'll go ahead and commit this work, but will note in the javadoc comment for this method that I think it's expensive. That way if anyone reviews tests later for performance issues she or he can more easily find it. [1] http://mail-archives.apache.org/mod_mbox/db-derby-dev/200703.mbox/[EMAIL PROTECTED] [2] http://mail-archives.apache.org/mod_mbox/db-derby-dev/200703.mbox/[EMAIL PROTECTED] Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, patch-2398.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1520) Document new SYSCS_DIAG tables
[ https://issues.apache.org/jira/browse/DERBY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482200 ] Jean T. Anderson commented on DERBY-1520: - With the new file committed on a Windows machine, the best step at this point would be to on a Windows machine do the svn propset svn:eol-style native filename, then a commit. That will create a minimal commit record with the propset change. UNIX users then do an 'svn up' and all should be well. Document new SYSCS_DIAG tables -- Key: DERBY-1520 URL: https://issues.apache.org/jira/browse/DERBY-1520 Project: Derby Issue Type: Sub-task Components: Documentation Affects Versions: 10.2.1.6 Reporter: Stan Bradbury Assigned To: Laura Stewart Attachments: derby1520_1.diff, derby1520_2.diff, derby1520_3.diff, derby1520_4.diff, refderby.ditamap, rrefsyscsdiagtables.html, rrefsyscsdiagtables.html See comments for DERBY-571 for initial documentation discussion. The new tables (mapped to the old Diagnostic VTIs) are: The old style syntax will remain in place for 10.2, but become deprecated. The tables to be implemented in this change are: SYSCS_DIAG.LOCK_TABLE replaces org.apache.derby.diag.LockTable SYSCS_DIAG.STATEMENT_CACHE replaces org.apache.derby.diag.StatementCache SYSCS_DIAG.TRANSACTION_TABLE replaces org.apache.derby.diag.TransactionTable SYSCS_DIAG.ERROR_MESSAGES replaces org.apache.derby.diag.ErrorMessages The information about the tables can be found in the javadoc for the class listed above. That can be found at: http://db.apache.org/derby/javadoc/engine/ click on the org.apache.derby.diag link in the Packages table, then select each class, e.g. LockTable to see the info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1520) Document new SYSCS_DIAG tables
[ https://issues.apache.org/jira/browse/DERBY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482212 ] Jean T. Anderson commented on DERBY-1520: - heh heh, then coming in late to the discussion I'm probably just creating confusion. :-) I'll check file settings, if I any are missing svn:eol-style native I'll post to derby-dev. Document new SYSCS_DIAG tables -- Key: DERBY-1520 URL: https://issues.apache.org/jira/browse/DERBY-1520 Project: Derby Issue Type: Sub-task Components: Documentation Affects Versions: 10.2.1.6 Reporter: Stan Bradbury Assigned To: Laura Stewart Attachments: derby1520_1.diff, derby1520_2.diff, derby1520_3.diff, derby1520_4.diff, refderby.ditamap, rrefsyscsdiagtables.html, rrefsyscsdiagtables.html See comments for DERBY-571 for initial documentation discussion. The new tables (mapped to the old Diagnostic VTIs) are: The old style syntax will remain in place for 10.2, but become deprecated. The tables to be implemented in this change are: SYSCS_DIAG.LOCK_TABLE replaces org.apache.derby.diag.LockTable SYSCS_DIAG.STATEMENT_CACHE replaces org.apache.derby.diag.StatementCache SYSCS_DIAG.TRANSACTION_TABLE replaces org.apache.derby.diag.TransactionTable SYSCS_DIAG.ERROR_MESSAGES replaces org.apache.derby.diag.ErrorMessages The information about the tables can be found in the javadoc for the class listed above. That can be found at: http://db.apache.org/derby/javadoc/engine/ click on the org.apache.derby.diag link in the Packages table, then select each class, e.g. LockTable to see the info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1520) Document new SYSCS_DIAG tables
[ https://issues.apache.org/jira/browse/DERBY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482226 ] Jean T. Anderson commented on DERBY-1520: - Ah, paying closer attention to Kim's comment: It's only the version that was attached after the issue was reopened. I wonder if the confusion might be with the patch files themselves. The patches Laura attaches to Jira are in Windows format. If somebody on a UNIX machine looks directly at the patch file, like I usually do with vi, you'll see the Windows end of lines. I usually run 'dos2unix' on the file before I look at it with vi, so I'm not distracted by the os-specific end of line. If I don't run dos2unix, the patch command itself will strip the Windows end of lines. At any rate, I checked and don't find any doc files in the doc trunk without the native setting. Document new SYSCS_DIAG tables -- Key: DERBY-1520 URL: https://issues.apache.org/jira/browse/DERBY-1520 Project: Derby Issue Type: Sub-task Components: Documentation Affects Versions: 10.2.1.6 Reporter: Stan Bradbury Assigned To: Laura Stewart Attachments: derby1520_1.diff, derby1520_2.diff, derby1520_3.diff, derby1520_4.diff, refderby.ditamap, rrefsyscsdiagtables.html, rrefsyscsdiagtables.html See comments for DERBY-571 for initial documentation discussion. The new tables (mapped to the old Diagnostic VTIs) are: The old style syntax will remain in place for 10.2, but become deprecated. The tables to be implemented in this change are: SYSCS_DIAG.LOCK_TABLE replaces org.apache.derby.diag.LockTable SYSCS_DIAG.STATEMENT_CACHE replaces org.apache.derby.diag.StatementCache SYSCS_DIAG.TRANSACTION_TABLE replaces org.apache.derby.diag.TransactionTable SYSCS_DIAG.ERROR_MESSAGES replaces org.apache.derby.diag.ErrorMessages The information about the tables can be found in the javadoc for the class listed above. That can be found at: http://db.apache.org/derby/javadoc/engine/ click on the org.apache.derby.diag link in the Packages table, then select each class, e.g. LockTable to see the info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1520) Document new SYSCS_DIAG tables
[ https://issues.apache.org/jira/browse/DERBY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482246 ] Jean T. Anderson commented on DERBY-1520: - Oh, it's a *real* line break causing confusion! :-) I agree with you that it isn't terrific -- it makes it look like many more changes occurred than actually did, making it less easy to verify changes. We have a somewhat similar issue with the derby web site. A small change in a source file may cause forrest to redo all the internal anchors in the generated html files. So it looks like changes to the html are much greater than they actually are, and they obscure the actual change. Document new SYSCS_DIAG tables -- Key: DERBY-1520 URL: https://issues.apache.org/jira/browse/DERBY-1520 Project: Derby Issue Type: Sub-task Components: Documentation Affects Versions: 10.2.1.6 Reporter: Stan Bradbury Assigned To: Laura Stewart Attachments: derby1520_1.diff, derby1520_2.diff, derby1520_3.diff, derby1520_4.diff, refderby.ditamap, rrefsyscsdiagtables.html, rrefsyscsdiagtables.html See comments for DERBY-571 for initial documentation discussion. The new tables (mapped to the old Diagnostic VTIs) are: The old style syntax will remain in place for 10.2, but become deprecated. The tables to be implemented in this change are: SYSCS_DIAG.LOCK_TABLE replaces org.apache.derby.diag.LockTable SYSCS_DIAG.STATEMENT_CACHE replaces org.apache.derby.diag.StatementCache SYSCS_DIAG.TRANSACTION_TABLE replaces org.apache.derby.diag.TransactionTable SYSCS_DIAG.ERROR_MESSAGES replaces org.apache.derby.diag.ErrorMessages The information about the tables can be found in the javadoc for the class listed above. That can be found at: http://db.apache.org/derby/javadoc/engine/ click on the org.apache.derby.diag link in the Packages table, then select each class, e.g. LockTable to see the info. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-2461) Convert lang/procedure.java to junit
Convert lang/procedure.java to junit Key: DERBY-2461 URL: https://issues.apache.org/jira/browse/DERBY-2461 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Priority: Minor Convert the lang/procedure.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-2461) Convert lang/procedure.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson reassigned DERBY-2461: --- Assignee: Jean T. Anderson Convert lang/procedure.java to junit Key: DERBY-2461 URL: https://issues.apache.org/jira/browse/DERBY-2461 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Convert the lang/procedure.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2398: Derby Info: [Patch Available] Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, patch-2398.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2458) Convert lang/unaryArithmeticDynamicParamter.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481772 ] Jean T. Anderson commented on DERBY-2458: - I took a look at your patch and have several comments. I like your addition of a assertColumnTypes method to JDBC.java. And I really like your use of assertions. Your usage of JDBC.assertFullResultSet, assertCompileError, and other methods is a good reminder to me to check where I should be using more of what others have already defined. Here are a couple things I think could be changed: - setUp() needs a stmt.close() - Two test methods create a SQL function, but don't drop it. I didn't encounter problems when I ran your suite (both client and embedded), but I wonder if that might create a problem in some context. - Take a pass through the code and verify that the javadoc comments match the code; I know how easy it is for them to get out of sync while developing. For example, the javadoc comment for setUp() doesn't match what it does. You might consider simplifying the description to something like Create and populate test tables.. That would reduce maintenance later if more tables get added, their names change, or more rows get inserted. Convert lang/unaryArithmeticDynamicParamter.java to junit - Key: DERBY-2458 URL: https://issues.apache.org/jira/browse/DERBY-2458 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: DERBY-2458_diff_03_16.txt, DERBY-2458_diff_ver1.txt, DERBY-2458_stat_ver1.txt Place holder to convert lang/unaryArithmeticDynamicParameter.java to junit -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[
https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean T. Anderson updated DERBY-2398:
Attachment: patch-2398.diff
Patch derby-2398.diff implements all tests. I'll wait for a day or two to give
anyone who has time/inclination to review it (and many thanks in advance).
Three specific questions/notes are below.
1) The original autoGeneratedJdbc30_app.properties file has this setting:
runwithj9=false
Does returning a empty suite if (!JDBC.vmSupportsJDBC3()) do what's needed for
j9? Or should I do something special?
2) I posted to derby-dev* asking if getGeneratedKeys() should return a NULL key
after commit/rollback. Depending on that answer, I'll open a Jira issue if one
is needed and update comments for the relevant methods in the code.
*
http://www.nabble.com/Should-getGeneratedKeys%28%29-return-a-NULL-key-after-commit-rollback--p9505841.html
3) The testResultSetGarbageCollection() method is noticeably slow (Test 20 in
the old code).
The purpose of the test was to verify a fix for an old issue in which the
ResultSet returned by getGenerateKeys() was incorrectly tied to the activation
of the PreparedStatement. So, when the ResultSet was garbage collected, the
activation was closed, resulting in an Activation closed, operation execute
not permitted exception on subsequent executes.
So, the test does this:
for (int i = 0; i 100; i++)
{
ps.setInt(1, 100+i);
ps.executeUpdate();
ResultSet rs = ps.getGeneratedKeys();
while (rs.next()) {
rs.getInt(1);
}
rs.close();
conn.commit();
System.runFinalization();
System.gc();
System.runFinalization();
System.gc();
}
I wonder if this is overkill. Could it be nipped back without degrading the
effectiveness of the test?
Convert jdbcapi/autoGeneratedJdbc30.java to junit
-
Key: DERBY-2398
URL: https://issues.apache.org/jira/browse/DERBY-2398
Project: Derby
Issue Type: Improvement
Components: Test
Reporter: Jean T. Anderson
Assigned To: Jean T. Anderson
Priority: Minor
Attachments: derby-2398-pre.diff, patch-2398.diff,
test_file_ignore_me.txt
Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to
junit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2454) Derby Doc Web pages - update FAQ, patch procedures, and tips on formatting
[ https://issues.apache.org/jira/browse/DERBY-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481438 ] Jean T. Anderson commented on DERBY-2454: - These changes look fine to me. Just one minor note -- there's a typo in docsfaq.xml : Tabs produce inconsisten output. I have one suggestion for dita.xml that isn't related to anything you changed. I added this guideline way back when: At the very least run ant html, ant monohtml and ant pdf to create HTML and PDF output (running ant all is best). I think it could be tweaked to be more helpful/reasonable (not necessary to build the books you didn't change): At the very least run 'ant manual_id' to create HTML and PDF output for the book you are changing. If you're interested in making that additional change, I'd appreciate it. Or I can catch that in my next round of web site edits. Derby Doc Web pages - update FAQ, patch procedures, and tips on formatting -- Key: DERBY-2454 URL: https://issues.apache.org/jira/browse/DERBY-2454 Project: Derby Issue Type: Improvement Components: Web Site Reporter: Laura Stewart Assigned To: Laura Stewart Attachments: derby2454.zip, docpages031507_2.diff Update the FAQ: - How to create cross-references to other topics, other books, and web sties - How to format code examples Update DITA page: - Improve instructions on Creating a patch - Improve instructions on Commiting a patch Update Guidelines page: - Add a section on Tips to Improve Output Formats -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2390) DOCS - Merge Working with Derby and Getting Started Guide
[ https://issues.apache.org/jira/browse/DERBY-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480883 ] Jean T. Anderson commented on DERBY-2390: - Regarding this: I'm glad you caught the problem with the term library. I don't think Derby is technically a product, which implies something that is sold; so maybe just Derby documentation would be a better title. The ASF requires every project to include a NOTICE file with this text [1]: Apache [PRODUCT_NAME] Copyright [] The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). Using the word product is not a problem. [1] http://www.apache.org/legal/src-headers.html#notice DOCS - Merge Working with Derby and Getting Started Guide - Key: DERBY-2390 URL: https://issues.apache.org/jira/browse/DERBY-2390 Project: Derby Issue Type: Improvement Components: Documentation Reporter: Laura Stewart Assigned To: Laura Stewart Attachments: cgsintro.html, rgsdocs17307.html The activities in the Working with Derby guide should be merged into the Getting Started Guide. Review Getting Started Guide for any reference info that should be either shared with another guide or moved to another guide. For example, the SQL Syntax section in the Getting Started Guide should be moved to the Reference Manual. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2398: Attachment: derby-2398-pre.diff derby-2398-pre.diff converts about half of jdbcapi/autoGeneratedJdbc30.java test to JUnit. 1) It adds a prepareStatement(String sql, int autoGeneratedKeys) method to junit/BaseJDBCTestCase.java. 2) This suite runs only if (JDBC.vmSupportsJDBC3()). Is checking for JDBC3 sufficient to handle J2ME/JSR169? --There's one test that will do a DriverManager call. 3) I made quite a few changes to the original test that are detailed below. For now, I have left in temporary System.out.println statements such as this: System.out.println (Old Test 1); // temporary along with prints of values to make it easy to doublecheck results against the original master. Changes to original program: 4) The original test did SET INCREMENT BY in ALTER statements because set by increment not yet supported for create table... The new JUnit test includes the increment in the CREATE TABLE statement. 5) There are many tests in the old version, roughly 25 * 4 queries each (most insert queries are tested four ways), so I divided them up into separate, standalone fixtures. However! This means each fixture creates its own Statement and PreparedStatement. The old master output this note: System.out.println(Test 8 - create a new statement and request for generated keys on it after doing an insert into ); This led me to think there might have been a difference in behavior between reusing the same Statement and create a new one, but I haven't see any difference in behavior compared to the original master. If the standalone fixtures path I'm on is not right, I'm only half way through the tests and it would be easy to redo the test so that a single fixture calls the separate test methods with the same Statements and PreparedStatements. Having separate methods will still make the test easier to read and follow. 6) I assume that what matters about the key generated is null vs. not-null value (I'm not paying attention to the actual values). That's simple, but if it's wrong I can change the code to test for actual values. Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480559 ] Jean T. Anderson commented on DERBY-2398: - 2) I think I can answer my own question: yes (I remembered belatedly that JDBC.vmSupportsJDBC2 was adequate for CallableTest.java) comments on the rest would be welcome. Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480564 ] Jean T. Anderson commented on DERBY-2398: - Incidently, in the old test, tests 11 and 12 output this message: expected to see resultset with one row of NULL value but instead get one row of non-NULL value from getGeneratedKeys Test 11 does a commit, followed by an insert into a table with no generated column. Test 12 does a rollback, followed by an insert into a table with no generated column. In both cases, the previous transaction had a one-row insert on a table with a auto-generated column. I don't know if that indicates a potential problem in Derby handling. I'll be sure to copy those comments into code comments in the JUnit version. Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480575 ] Jean T. Anderson commented on DERBY-2398: - Dan wrote: Testing the values is best as the purpose (I assume) of this test is to test the JDBC feature that returns auto genrated keys, so checking it's returning the correct value would be good. ack, the old test 13 needs to verify that the value obtained inside a savepoint is the same after it does a rollback. I had missed that fine point, so I do need to check actual values. thanks for the feedback, Dan. Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2398-pre.diff, test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson resolved DERBY-2428. - Resolution: Fixed Assignee: Jean T. Anderson I believe these changes are stable. Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479635 ] Jean T. Anderson commented on DERBY-2428: - ok, this is truly strange. I clicked on all the MD5 signature links last night and didn't find any of them missing at all, but you're right -- the 10.1.3.1 MD5 sig files are missing this morning. --Incidently, it was in clicking on all the archive signature links that I discovered the missing PGP sigs. I'm finding these PGP signature files still missing: http://archive.apache.org/dist/dist/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-lib.tar.gz.asc http://archive.apache.org/dist/dist/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-lib-debug.tar.gz.asc http://archive.apache.org/dist/dist/db/derby/db-derby-10.1.2.1/db-derby-10.1.2.1-lib.tar.gz.asc Re derby_downloads.html, what about renaming the section Previous Official Releases to Archive Official Releases? --And move 10.2.1.6 to point to the archives? Derby is down to 199016 (from 383158): 96890 db-derby-10.2.1.6 102106 db-derby-10.2.2.0 It's still a lot of space to consume on the mirrors. Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479671 ] Jean T. Anderson commented on DERBY-2428: - Thanks for the eagle eye! double dists fixed in revision 516488. Re moving 10.2.1.6, I'll wait until we know what to do with the md5 sigs. I assume we can manually copy those to the archive (and avoid broken links). But the right thing might be to remove them from the download files. Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479721 ] Jean T. Anderson commented on DERBY-2428: - Joshua Slive fixed it so the md5s are now archived; I'll go ahead and switch 10.2.1.6. Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1250) Harmonize repositioning requirement of FORWARD_ONLY and SCROLL_INSENSITIVE updatable result set after updateRow
[ https://issues.apache.org/jira/browse/DERBY-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-1250: Attachment: test_file_ignore_me.txt Testing to see if file upload works. Harmonize repositioning requirement of FORWARD_ONLY and SCROLL_INSENSITIVE updatable result set after updateRow --- Key: DERBY-1250 URL: https://issues.apache.org/jira/browse/DERBY-1250 Project: Derby Issue Type: Improvement Components: JDBC, Network Client Affects Versions: 10.0.2.0 Reporter: Dag H. Wanvik Priority: Minor For forward-only result sets, in the reference manual, under JDBC Reference, java.sql.Resultset (the second section with that name, btw!), Table1: JDBC 2.0 ResultSet Methods Supported, updateRow, one can read : After the row is updated, the ResultSet object will be positioned before the next row. Before issuing any methods other than close on the ResultSet object, the program will need to reposition the ResultSet object by using the next() method. Presently, for scrollable insensitive result sets, there is no such requirement. These behaviors should be harmonized, to maximize ease-of-use. See also the discussion of this in the review thread of DERBY-775. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-1250) Harmonize repositioning requirement of FORWARD_ONLY and SCROLL_INSENSITIVE updatable result set after updateRow
[ https://issues.apache.org/jira/browse/DERBY-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-1250: Attachment: (was: test_file_ignore_me.txt) Harmonize repositioning requirement of FORWARD_ONLY and SCROLL_INSENSITIVE updatable result set after updateRow --- Key: DERBY-1250 URL: https://issues.apache.org/jira/browse/DERBY-1250 Project: Derby Issue Type: Improvement Components: JDBC, Network Client Affects Versions: 10.0.2.0 Reporter: Dag H. Wanvik Priority: Minor For forward-only result sets, in the reference manual, under JDBC Reference, java.sql.Resultset (the second section with that name, btw!), Table1: JDBC 2.0 ResultSet Methods Supported, updateRow, one can read : After the row is updated, the ResultSet object will be positioned before the next row. Before issuing any methods other than close on the ResultSet object, the program will need to reposition the ResultSet object by using the next() method. Presently, for scrollable insensitive result sets, there is no such requirement. These behaviors should be harmonized, to maximize ease-of-use. See also the discussion of this in the review thread of DERBY-775. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2398: Attachment: test_file_ignore_me.txt test upload Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: test_file_ignore_me.txt Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479749 ] Jean T. Anderson commented on DERBY-2428: - Switched the 10.2.1.6 downloads to archive.apache.org, revision 516558. Andrew restored the md5s for 10.1.3.1, so it looks like everything is stable (whew!). And derby disk consumption on the mirrors is down to 102126 (from 383158 originally). Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2424) Problem with appauth_os.jpg graphics file in Developer's Guide
[ https://issues.apache.org/jira/browse/DERBY-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2424: Attachment: test_file_ignore_me.txt testing file upload Problem with appauth_os.jpg graphics file in Developer's Guide -- Key: DERBY-2424 URL: https://issues.apache.org/jira/browse/DERBY-2424 Project: Derby Issue Type: Bug Components: Documentation Reporter: Kim Haase Assigned To: Laura Stewart Attachments: appauth_os.jpg, test_file_ignore_me.txt The appauth_os.jpg file is used in the PDF and monohtml versions of the Dev Guide, in the section Working with user authentication. Currently it does not appear in these versions of the book. (The GIF version of the file, used in the HTML Pages version, does appear.) When I try to display the file in a graphics viewer, it doesn't appear. When I use the Unix command file on the file, it reports the following: % file appauth_os.jpg appauth_os.jpg: java program For the other JPEG files it reports the file type as either data or JPEG file. So I think this file needs to be recreated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.3.1, 10.1.2.1, 10.1.1.0 Reporter: Jean T. Anderson Derby releases are consuming much space on the Apache mirrors. It's time to move older releases to the archives. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2428: Description: Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . (was: Derby releases are consuming much space on the Apache mirrors. It's time to move older releases to the archives.) Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479463 ] Jean T. Anderson commented on DERBY-2428: - Below is a chat Jean and Andrew had on #derby. Relevant points (I think) are: - All releases are automatically copied to the archives; we just need to update the web pages pointing to them. - Everything but the current release is a candidate for being pointed at the archives. - Download pages can be updated one by one (no need to do all in one blast). - Andrew identified these steps for updating a download page: 1) remove the mirror selection section and form from the HTML page, 2) replace [preferred] with http://archive.apache.org/, and 3) then make the derby_downloads page link directly to the HTML and not the cgi. 4) And then remove the cgi script for that release. Also, once the dowload page for a release has been updated, we need to physically remove the release from /www/www.apache.org/dist/db/derby on people.a.o. Below is the complete chat: samcintyre jta: now that I think about it, 10.2.1.6 should probably be archived as well. There's no reason anyone should download 10.2.1.6 instead of 10.2.2.0. jta sure -- why not archive everything previous to the most current release? jta dumb question: are archives mirrored? jta more the question is: how big is the update to the download pages for the older releases? samcintyre jta: seems like a good idea to keep the most recent release per active branch. samcintyre hmm. jta that sounds fine -- just moving the oldest to the archives would help free space samcintyre Except can't really call the 10.1 branch active, since we can't release from it without overhauling all the license headers, and I don't think there'd be much interest in doing that. jta :-) samcintyre Anyway, keeping latest on branch for current_branch + (current_branch - 1) seems like a good policy. samcintyre 10.2.1.6 itself is almost a hundred megs. samcintyre keeping just 10.1.3.1 and 10.2.0.0 would drop derby's disk usage from 380M to 175M samcintyre (meant 10.2.2.0 there) jta any reason to keep 10.1.3.1 on the mirrors? if it's available from the archives? samcintyre oh, as for your other question: are archives mirrored? samcintyre no, it's more like the mirrors are archived. Anything put into /www/www.apache.org/dist is automatically copied to /www/archive.apache.org/dist jta that would be an issue if there were vast downloads for a release in the archives, but that seems unlikely for a 10.1 release samcintyre nah, i guess not, people mostly just want the latest, i would assume.jta I'd expect the highest download hits against the latest jta maybe an occasional hit against the archives. if a problem came up and we anticipated lots of downloads for a prior release, we could always move it back to the mirrors, right? samcintyre true samcintyre so the changes would be pretty straightforward, though there are several: remove the mirror selection section and form from the HTML page, replace [preferred] with http://archive.apache.org/, and then make the derby_downloads page link directly to the HTML and not the cgi. And then remove the cgi script for that release. jta at least it could be reviewed before being published. :-) jta There's some work, which won't be instantaneous. want me to open a jira issue? samcintyre yes, please. that'll give others an opportunity to pick it up. jta sounds good samcintyre (not much time to do it today, probably wouldn't get to it until late next week if it were left up to me) jta and they don't have to be moved all at once samcintyre although, i'd have time to review if somebody posted a patch. samcintyre true jta I opened DERBY-2428, I'll attach our IRC chat to a comment Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Derby releases are consuming much space on the Apache mirrors. It's time to move older releases to the archives. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2428: Attachment: release-10.1.1.0.diff release-10.1.1.0.diff is a patch that points the 10.1.1.0 downloads to the archives. Here are the files that changed: [EMAIL PROTECTED] trunk]$ svn stat src D src/documentation/content/xdocs/releases/release-10.1.1.0.cgi M src/documentation/content/xdocs/releases/release-10.1.1.0.html M src/documentation/content/xdocs/derby_downloads.xml Does it look like I caught everything? Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479471 ] Jean T. Anderson commented on DERBY-2428: - thanks for the quick feedback! I also missed replacing [preferred] for the plugins, so will catch those. Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479475 ] Jean T. Anderson commented on DERBY-2428: - ok, I committed the change for the 10.1.1.0 download in revision 516249. and did the 'svn up' on people. After I verify it works, I'll remove that distribution from www.apache.org/dist. one note: because of the local trickery we do up on people to make the mirror magic work, there was a conflict: [EMAIL PROTECTED] /www/db.apache.org/derby]$ svn up Uderby_downloads.html Dreleases/release-10.1.1.0.cgi Creleases/release-10.1.1.0.html Updated to revision 516249. I reverted that file: [EMAIL PROTECTED] /www/db.apache.org/derby]$ svn revert releases/release-10.1.1.0.html Reverted 'releases/release-10.1.1.0.html' [EMAIL PROTECTED] /www/db.apache.org/derby]$ svn up At revision 516249. It's good to test this strategy with the oldest release. :-) Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2428) Move older releases from www.apache.org/dist/ to archive.apache.org/dist
[ https://issues.apache.org/jira/browse/DERBY-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479493 ] Jean T. Anderson commented on DERBY-2428: - In switching the 10.1.2.1 and 10.1.3.1 downloads to the archives, spotted these missing signature files: dist/db/derby/db-derby-10.1.2.1/db-derby-10.1.2.1-lib.tar.gz.asc dist/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-lib.tar.gz.asc dist/db/derby/db-derby-10.1.3.1/db-derby-10.1.3.1-lib-debug.tar.gz.asc committed changes for 10.1.2.1 in revision 516274 and for 10.1.3.1 in revision 516279. Move older releases from www.apache.org/dist/ to archive.apache.org/dist Key: DERBY-2428 URL: https://issues.apache.org/jira/browse/DERBY-2428 Project: Derby Issue Type: Task Components: Web Site Affects Versions: 10.1.1.0, 10.1.2.1, 10.1.3.1 Reporter: Jean T. Anderson Attachments: release-10.1.1.0.diff Derby releases are consuming much space on the Apache mirrors. It's time to update the older download pages to point to the archives, then remove them from www.apache.org/dist/ . -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-2398) Convert jdbcapi/autoGeneratedJdbc30.java to junit
Convert jdbcapi/autoGeneratedJdbc30.java to junit - Key: DERBY-2398 URL: https://issues.apache.org/jira/browse/DERBY-2398 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Convert the jdbcapi/autoGeneratedJdbc30.java test from the old harness to junit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2390) DOCS - Merge Working with Derby and Getting Started Guide
[ https://issues.apache.org/jira/browse/DERBY-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478138 ] Jean T. Anderson commented on DERBY-2390: - If you decide to name it Derby tutorial, please just give me a heads up and I'll rename http://db.apache.org/derby/papers/DerbyTut/index.html to something suitable so the two don't get confused with each other. heh -- I only just now noticed that none of the Derby books have Apache included in the title. I wonder if that should change moving forward. DOCS - Merge Working with Derby and Getting Started Guide - Key: DERBY-2390 URL: https://issues.apache.org/jira/browse/DERBY-2390 Project: Derby Issue Type: Improvement Components: Documentation Reporter: Laura Stewart Assigned To: Laura Stewart The activities in the Working with Derby guide should be merged into the Getting Started Guide. Review Getting Started Guide for any reference info that should be either shared with another guide or moved to another guide. For example, the SQL Syntax section in the Getting Started Guide should be moved to the Reference Manual. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2390) DOCS - Merge Working with Derby and Getting Started Guide
[ https://issues.apache.org/jira/browse/DERBY-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478168 ] Jean T. Anderson commented on DERBY-2390: - The web-based tutorial now at http://db.apache.org/derby/papers/DerbyTut/index.html was originally developed for ApacheCon, not for the doc set. It's starting to become obsolete -- for example, needs to be updated for 10.2.2.0 features (it uses the old scripts, doesn't say anything about derbyrun.jar). If your new effort can replace it, terrific. I'd be happy to remove it. DOCS - Merge Working with Derby and Getting Started Guide - Key: DERBY-2390 URL: https://issues.apache.org/jira/browse/DERBY-2390 Project: Derby Issue Type: Improvement Components: Documentation Reporter: Laura Stewart Assigned To: Laura Stewart The activities in the Working with Derby guide should be merged into the Getting Started Guide. Review Getting Started Guide for any reference info that should be either shared with another guide or moved to another guide. For example, the SQL Syntax section in the Getting Started Guide should be moved to the Reference Manual. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2248) Place holder for the NetworkServer system test
[ https://issues.apache.org/jira/browse/DERBY-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477371 ] Jean T. Anderson commented on DERBY-2248: - This contribution is cleared for import. Here's the final notice sent to the Incubator: http://mail-archives.apache.org/mod_mbox/incubator-general/200703.mbox/[EMAIL PROTECTED] Place holder for the NetworkServer system test -- Key: DERBY-2248 URL: https://issues.apache.org/jira/browse/DERBY-2248 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 Attachments: build.xml, DERBY-2248_diff.txt, DERBY-2248_stat.txt, NsTest.zip I will be using this Jira entry as the place holder for the contibution of NetworkServer system tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2276) ApacheCon 2006 presentations
[ https://issues.apache.org/jira/browse/DERBY-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476639 ] Jean T. Anderson commented on DERBY-2276: - In revision 512832 committed RHansenApacheConFinal#WE30pdf.pdf as RHansenApacheCon-2006.pdf and Apache_Derby10_2_Whats_New.ppt as Apache_Derby10_2_Whats_New-2006.ppt in case anyone is presenting at ApacheCon EU 2007 in Amsterdam with updated presentations. Note Rebecca's notification to derby-dev about sending her presentation to Rick Hillegas, who uploaded it to DERBY-2276: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200702.mbox/[EMAIL PROTECTED] ApacheCon 2006 presentations Key: DERBY-2276 URL: https://issues.apache.org/jira/browse/DERBY-2276 Project: Derby Issue Type: Task Components: Web Site Reporter: Rick Hillegas Attachments: Apache_Derby10_2_Whats_New.ppt, DerbyPerfDurability.pdf, JavaInTheDatabase.pdf, RHansenApacheConFinal#WE30pdf.pdf This is a place to attach our presentations for ApacheCon 2006. Thanks to Jean for volunteering to wire these into the web site. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476642 ] Jean T. Anderson commented on DERBY-2304: - Dan wrote: : Jean Tests that get/set BigDecimal only run if (!JDBC.vmSupportsJSR169()) : : That should really be if (JDBC.vmSupportsJDBC2()) since the fixture is testing methods that are in JDBC 2. thanks for the clarification, Dan! That nicely declutters the suite code. Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff, derby-2304-preview.diff, derby-2304.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2304: Attachment: derby-2304.diff (Never go on vacation -- it sets you behind by the amount you spent off * 2.) I'm attaching derby-2304.diff, which incorporates the feedback I've received: 1) Tests that get/set BigDecimal only run if (!JDBC.vmSupportsJSR169()) 2) Tests that need DriverManager only run if (JDBC.vmSupportsJDBC2()) 3) The assertDecimalSameValue method wraps the BigDecimal.compareTo() call (I'll pass for now on trying to get an equality check working). I think one of the tests from derbynet/callable.java is dubious and I would appreciate opinions -- I included it in the patch as testSystemOutPrintlnProc() . The sql procedure it invokes just does this: System.out.println(I'm doing something here...); So, of course, the window in which you run the junit test gets: I'm doing something here... I'm doing something here... I somehow suspect System.out.println in a junit test isn't good, but I thought I'd ask. If there's no feedback, I'm inclined to commit these changes with that test disabled. And, of course, I'd appreciate any other observations anyone has. Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff, derby-2304-preview.diff, derby-2304.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson closed DERBY-2237. --- Resolution: Fixed Fix Version/s: 10.3.0.0 10.2.2.1 Assignee: Jean T. Anderson 1) Scott Hutinger fixed the problem with the empty Copyright string in the header in the PDF books in DERBY-2275. 2) Source files with the old style copyright were fixed in revisions 495755 (trunk) and 495756 (10.2 branch). 3) The copyright tags mentioned in the description don't actually get used. 4) The copyright notice was corrected and a license page added to the books in trunk revisions 502474 (English), 502765 (Japanese), and 504638 (Brazilian Portuguese). The changes for English and Portuguese were merged to the 10.2 branch with revisions 509777 and 509785. (The Japanese doc isn't in the 10.2 branch.) Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Assigned To: Jean T. Anderson Priority: Blocker Fix For: 10.2.2.1, 10.3.0.0 Attachments: copyright-2237-1.diff, copyright-2237-html-1.zip, copyright-2237-html-pt_BR.zip, copyright-2237-pt_BR.diff, dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472332 ] Jean T. Anderson commented on DERBY-2304: - Yes, you're absolutely right about the naming confusion. Naming the method I have working so far, which uses compareTo, assertDecimalSameValue would make far more sense. So far I haven't had success with an equality operation, even with variations on scale and roundingMode as in: BigDecimal expected = (new BigDecimal(val1)); expected = expected.setScale(4); // the procedure uses DECIMAL(14,4) or: expected = expected.setScale(4, BigDecimal.ROUND_HALF_UP); // 8 rounding modes then: assertEquals(msg, val1, val2); I'll keep working on an equality check. Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff, derby-2304-preview.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2304) Convert derbynet/callable.java to junit
[
https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472176
]
Jean T. Anderson commented on DERBY-2304:
-
Following up on Dan's suggestion to implement a assertDecimalEquals method,
this works:
public void assertDecimalEquals (String msg, String val1, BigDecimal val2)
{
BigDecimal expected = (new BigDecimal(val1));
assertTrue(msg +
expected: + val1 + but was: + val2.toString() + ,
expected.compareTo(val2)==0);
}
It gets called like this:
assertDecimalEquals(OUT 2, 33.3330,cs.getBigDecimal(2));
If an assert fails, it outputs a message that is consistent with the style of
other assertEquals messages:
OUT 9 expected: -. but was -.
Does anyone spot any problems with this approach?
Convert derbynet/callable.java to junit
---
Key: DERBY-2304
URL: https://issues.apache.org/jira/browse/DERBY-2304
Project: Derby
Issue Type: Improvement
Components: Test
Reporter: Jean T. Anderson
Assigned To: Jean T. Anderson
Priority: Minor
Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff,
derby-2304-preview.diff
Convert the derbynet.callable.java test to the junit framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472179 ] Jean T. Anderson commented on DERBY-2304: - Thanks for the J2ME comments, Myrna! I suspect that for the moment I'm best off excluding JSR169 until I have the entire test converted and can see what is and is not supported. Thanks for pointing it out. Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff, derby-2304-preview.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2248) Place holder for the NetworkServer system test
[ https://issues.apache.org/jira/browse/DERBY-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471534 ] Jean T. Anderson commented on DERBY-2248: - The software grant for this contribution was received, it just hasn't been recorded yet. I suggest that Manjula go ahead and upload the code when it's ready so people can start looking at it. It just can't be committed until the ip clearance process is complete (including the software grant recorded). Place holder for the NetworkServer system test -- Key: DERBY-2248 URL: https://issues.apache.org/jira/browse/DERBY-2248 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.3.0.0 Reporter: Manjula Kutty Assigned To: Manjula Kutty Priority: Trivial Fix For: 10.3.0.0 I will be using this Jira entry as the place holder for the contibution of NetworkServer system tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-2304) Convert derbynet/callable.java to junit
Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2304) Convert derbynet/callable.java to junit
[
https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean T. Anderson updated DERBY-2304:
Attachment: derby-2304-preview.diff
I'm working on a CallableTest.java to convert derbynet/callable.java to junit.
derby-2304-preview.diff is way incomplete, but I'm looking for feedback on the
overall structure and implementation so far. I summarized issues down below.
So far, CallableTest.java implements just 3 tests (and only runs 2 tests -- see
issue #4 down below).
The code tries to model itself after DatabaseMetaDataTest.java for reducing try
{} clutter, and after ProcedureTest.java for its basic setup, which creates all
the SQL objects up front and doesn't tear them down -- and also enables one of
the tests to run in the client framework (see issue #1). I may have gone
overboard in some cases and misunderstood stuff so please be picky!
I'm reorganizing the original test in the following ways:
- Move it from derbynet to jdbcacpi because I think it should be able to run
under both embedded and client frameworks.
- Carve it up into smaller tests.
- Create more descriptive function/procedure/method/table names like
ProcedureTest.java does; for example, instead of CREATE FUNCTION method2
calling method2 I have CREATE FUNCTION ONE_IN_ONE_OUT_FUNC which calls
OneInOneOutFunc and the method that tests it is testOneInOneOutFunc.
I ran into these issues:
1) derbynet/callable.java
Line 92 of the original test comments out the cleanup:
// stmt.execute(DROP FUNCTION method2);
I discovered that this DROP statement works fine in embedded, but raises this
exception in the client:
'DROP ROUTINE' cannot be performed on object 'ONE_IN_INE_OUT_FUNC' because
there is an open resultSet dependent on that object.
Does this error ring a bell with anyone?
ProcedureTest.java sets up everything at the start and there is no teardown, so
that's the approach I adopted with CallableTest.java. That approach enables
this test to run without error (the error did occur with my first attempt that
implemented create/drops in setup() and tearDown() methods). But I'm
uncomfortable about masking the DROP error, wonder if the current strategy will
be solid for all test scenarios.
2) Because of the client problem in #1 I initially set up baseSuite() to not
run that test in client; however, I discovered that usingEmbedded() is always
true, so I did a Hack! doing a string compare on embedded / client. Is this
the wrong place to exclude the run of a specific test for a given framework?
3) I created a local assertEquals(byte[] b1, byte[] b2) for the byte comparison
in testUpdateLongBinaryProc() . Is there already a way to get support for byte
comparisons? I didn't spot any. If not, is this something I should move to
BaseJDBCTestCase.java (and also completely implement)?
4) testBigDecimalInAndOutParameters() doesn't get called yet -- I need to spin
up on how to do assertEquals with BigDecimal.
For example, this assert:
assertEquals(OUT 2, new BigDecimal(33.3330), cs.getBigDecimal(2));
generates this:
OUT 2 expected:33.33299840838 but was:33.3330
I'll probably start a thread on derby-dev to ask about the original objectives
of that test. I grew a little puzzled looking at it.
Convert derbynet/callable.java to junit
---
Key: DERBY-2304
URL: https://issues.apache.org/jira/browse/DERBY-2304
Project: Derby
Issue Type: Improvement
Components: Test
Reporter: Jean T. Anderson
Assigned To: Jean T. Anderson
Priority: Minor
Attachments: derby-2304-preview.diff
Convert the derbynet.callable.java test to the junit framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471058 ] Jean T. Anderson commented on DERBY-2237: - Committed changes to the Brazilian Portuguese translations to the trunk, revision 504638. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: copyright-2237-1.diff, copyright-2237-html-1.zip, copyright-2237-html-pt_BR.zip, copyright-2237-pt_BR.diff, dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471141 ] Jean T. Anderson commented on DERBY-2304: - Thanks for the speedy comments, Dan! R1) Regarding the teardown, I was confused by what was happening under the hood and when. The 'DROP ROUTINE' error I encountered sounds like something I should reproduce separately and log as an issue. R2) I really like your approach that avoids explicitly adding all fixtures. R3) Excellent -- thanks! R4) assertDecimalEquals(OUT 2, 33.3330, cs.getBigDecimal(2)); That still resulted in differences detected: OUT 2 expected:33.3330 but was:33.3330 However, changing the last arg to string worked: assertDecimalEquals(OUT 2, 33.3330, cs.getBigDecimal(2).toString()); thanks for the feedback! Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2304: Attachment: derby-2304-preview-2.diff derby-2304-preview-2.diff incorporates feedback from Dan. Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2304: Attachment: derby-2304-preview-3.diff Don't look at derby-2304-preview-2.diff -- it has confusing cruft leftover from my initial teardown implementation [1]. derby-2304-preview-3.diff cleans that up. [1] For newbies coming after me, my first shot at CallableTest.java explicitly coded both setUp() and tearDown(). But I switched the strategy to use CleanDatabaseTestSetup() instead, which automatically does the tearDown, eliminating any need to provide code to drop database objects. Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff, derby-2304-preview.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2304) Convert derbynet/callable.java to junit
[ https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471157 ] Jean T. Anderson commented on DERBY-2304: - Dan asked: On the assertDecimalEquals() how were you comparing the string to the BigDecimal? I goofed -- I was moving too quickly and didn't pay close enough attention to your assertDecimalEquals() suggestion. I did this, which was silly: assertEquals(OUT 2, 33.3330, cs.getBigDecimal(2)); This code passes on 1.4.2, but it can't be reliable: assertEquals(OUT 2, 33.3330, cs.getBigDecimal(2).toString()); I'll slow down and work on a real decimal comparison solution. Thanks for all the help! Convert derbynet/callable.java to junit --- Key: DERBY-2304 URL: https://issues.apache.org/jira/browse/DERBY-2304 Project: Derby Issue Type: Improvement Components: Test Reporter: Jean T. Anderson Assigned To: Jean T. Anderson Priority: Minor Attachments: derby-2304-preview-2.diff, derby-2304-preview-3.diff, derby-2304-preview.diff Convert the derbynet.callable.java test to the junit framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2237: Attachment: copyright-2237-html-pt_BR.zip copyright-2237-pt_BR.diff This patch syncs up the Brazilian Portuguese docs with the English changes in revision 502474. Files: copyright-2237-pt_BR.diff -- patch for all 3 books copyright-2237-html-pt_BR.zip -- review html for just the Getting Started guide If anyone spots any problems, please let me know. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: copyright-2237-1.diff, copyright-2237-html-1.zip, copyright-2237-html-pt_BR.zip, copyright-2237-pt_BR.diff, dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469890 ] Jean T. Anderson commented on DERBY-2237: - I corrected the Copyright line and notice on the Copyright page in the Japanese translation of the Getting Started guide in the trunk, revision 502765. I didn't attempt to add the license page even though it's in English. That would require adding the file to the ditamap and I don't know how to set the navtitle in Japanese. In any case, correcting the copyright is the most important thing. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: copyright-2237-1.diff, copyright-2237-html-1.zip, copyright-2237-html-pt_BR.zip, copyright-2237-pt_BR.diff, dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2237: Attachment: copyright-2237-html-1.zip copyright-2237-1.diff Here is a first shot at rewording the copyright notice and adding the apache license, like the http project does, initially just for the Getting Started guide. copyright-2237-1.diff - svn diff (patch -p0 at the trunk level) copyright-2237-html-1.zip (html pages: index, toc, copyright and license) In keeping with the http project, I ended up making the license a separate page (separate topic). The http project spent a lot of time fussing to make the format of the license text pretty (for example, see http://httpd.apache.org/docs/2.2/license). I spent long enough fussing to realize that obtaining a pretty format is non trivial, so included it as a codeblock. It's ok in the html and definitely clunky in the PDF because some of the text is just long enough to wrap. Thoughts? Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: copyright-2237-1.diff, copyright-2237-html-1.zip, dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469653 ] Jean T. Anderson commented on DERBY-2237: - I shortened the line length for the Apache license so at least the lines don't wrap on the PDF (doesn't look quite so clunky), and committed changes to the trunk for the English manuals, revision 502474. I still need to update the Brazilian Portuguese and Japanese translations. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: copyright-2237-1.diff, copyright-2237-html-1.zip, dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2276) ApacheCon 2006 presentations
[ https://issues.apache.org/jira/browse/DERBY-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468651 ] Jean T. Anderson commented on DERBY-2276: - Added JavaInTheDatabase.pdf as JavaInTheDatabase-2006.pdf in revision 501126. Added DerbyPerfDurability.pdf as DerbyPerfDurability-2006.pdf in revision 501421. Added links to two more papers that Dan Debrunner posted [1] in revision 501201. [1] http://mail-archives.apache.org/mod_mbox/db-derby-dev/200701.mbox/[EMAIL PROTECTED] ApacheCon 2006 presentations Key: DERBY-2276 URL: https://issues.apache.org/jira/browse/DERBY-2276 Project: Derby Issue Type: Task Components: Web Site Reporter: Rick Hillegas Attachments: DerbyPerfDurability.pdf, JavaInTheDatabase.pdf This is a place to attach our presentations for ApacheCon 2006. Thanks to Jean for volunteering to wire these into the web site. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2227) Web Site - Add Checklist page for Doc updates for each release
[ https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468428 ] Jean T. Anderson commented on DERBY-2227: - This looks good, Laura, I just have one suggestion. Instead of this: Check with Apache for any updates to the copyright wording. Change it to this when you commit it: Check with derby-dev for any updates to the copyright wording. One tricky thing about committing web site changes is sometimes more pages get modified than you explicitly changed. This can be confusing. For example, you should see something like this below: $ svn stat src build/site M src/documentation/content/xdocs/manuals/docsfaq.xml A src/documentation/content/xdocs/manuals/docscheck.xml M src/documentation/content/xdocs/site.xml M build/site/linkmap.html M build/site/manuals/docsfaq.html M build/site/manuals/dita.html A build/site/manuals/docscheck.html M build/site/manuals/index.html M build/site/manuals/messages.html M build/site/manuals/guidelines.html More pages changed under build/site/manuals than what you explicitly changed because of your update to site.xml. Adding the new page, docscheck.xml, to the site menu causes the navigation to change for all pages on the documentation tab. I suggest you go ahead and commit. Web Site - Add Checklist page for Doc updates for each release -- Key: DERBY-2227 URL: https://issues.apache.org/jira/browse/DERBY-2227 Project: Derby Issue Type: Improvement Components: Web Site Reporter: Laura Stewart Assigned To: Laura Stewart Priority: Minor Attachments: Derby2227-1.diff, derby2227-1.zip, derby2227-2.diff, derby2227-2.zip, docscheck.html, site.xml Create a list of items to check and update for each release for the documentation. This list should include copywrite info, dates/time issues in the Working with Derby See this thread: http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2227) Web Site - Add Checklist page for Doc updates for each release
[ https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468432 ] Jean T. Anderson commented on DERBY-2227: - Yes; the built pages must be committed. Step 8 at http://db.apache.org/derby/papers/derby_web.html suggests this: svn commit --message here is my commit message src build/site I usually put the commit info into a file called /tmp/changes.txt, then commit like this: svn commit --file /tmp/changes.txt src build/site You must commit the built changes because the built site is checked out of svn on people.apache.org. Step 9 then walks you through publishing the changes on people.apache.org. Web Site - Add Checklist page for Doc updates for each release -- Key: DERBY-2227 URL: https://issues.apache.org/jira/browse/DERBY-2227 Project: Derby Issue Type: Improvement Components: Web Site Reporter: Laura Stewart Assigned To: Laura Stewart Priority: Minor Attachments: Derby2227-1.diff, derby2227-1.zip, derby2227-2.diff, derby2227-2.zip, docscheck.html, site.xml Create a list of items to check and update for each release for the documentation. This list should include copywrite info, dates/time issues in the Working with Derby See this thread: http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468064 ] Jean T. Anderson commented on DERBY-2237: - Thanks so much for looking at this, Halley. I think the Brazilian copyrights need to go from this: Copyright 2004, 2006 The Apache Software Foundation ou seus licenciadores, conforme se aplique. to this: Copyright 2004, 2006 The Apache Software Foundation And I think the text that is already committed is correct because it matches http://www.apache.org/licenses/LICENSE-2.0.html#apply . Could you confirm that? Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468078 ] Jean T. Anderson commented on DERBY-2237: - Thanks, Halley, that's what I thought. --The Derby 10.1 docs also include that boilerplate notice, but the Copyright line itself had the additional or its licensors, as applicable. wording, which needed to be dropped in 10.2 for reasons I won't go into. We'll get it untangled. I'm about to post another comment with a suggestion for the English docs, and I suggest you hold off doing anymore until a decision gets made. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468081 ] Jean T. Anderson commented on DERBY-2237: - I've done a little more research on the HTTP project and looked at current doc source to see if anything has changed for the end user (I believe nothing has changed). 1) The pdf's include - a copy of the 2.0 license text from http://www.apache.org/licenses/LICENSE-2.0 - the boilerplate notice from http://www.apache.org/licenses/LICENSE-2.0.html#apply , but only the first part of it (through the URL, ommitting the last paragraph). I'm guessing that the PDFs might in part do this because no where in the Apache License 2.0 is the URL for the license provided. 2) The html docs include - a copy of the 2.0 license text from http://www.apache.org/licenses/LICENSE-2.0 - the footer of each page has this, with the second line linked to http://www.apache.org/licenses/LICENSE-2.0.html: Copyright 2006 The Apache Software Foundation. Licensed under the Apache License, Version 2.0. I found the decision regarding the footer for html generated from xml at http://mail-archives.apache.org/mod_mbox/httpd-docs/200402.mbox/[EMAIL PROTECTED] 3) The Apache License itself isn't translated -- it gets included in English in all the translated docs. I'd like to float a suggestion. Since the Derby docs do not currently include a copy of the Apache License 2.0, I suggest modifying the copyright page for each book to include the first part of the boilerplate like the HTTP PDFs do so that the URL is publicized (but noting the Derby years, of course): Copyright 2004-2006 The Apache Software Foundation. Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Then include a license subsection containing the complete text of the Apache License 2.0 (only in English). This would get the base information into all doc types (PDF, html book, and html). We should still additionally look into doing a footer for the html pages that links to the Apache License, but that requires someone with DITA expertise, whereas I could myself make the suggested change. What do people think? If I hear no feedback to the contrary in a couple days, I'll go ahead and make the changes as I suggested. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz, pt_BR_copyright.diff, pt_BR_copyright.diff.html, radmincopyright.html, rgscopyright.html, rrefcopyright.html Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467865 ] Jean T. Anderson commented on DERBY-2237: - These files in the Brazilian Portuguese translations of the Derby docs have the old style copyright dates and apache license notice: https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/pt_BR/adminguide/radmincopyright.dita https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/pt_BR/getstart/rgscopyright.dita https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/pt_BR/ref/rrefcopyright.dita They need to be brought up to date with their English counterparts: https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/adminguide/radmincopyright.dita https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/getstart/rgscopyright.dita https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/ref/rrefcopyright.dita If somebody can step forward and do the updates, please let us know. Otherwise, I plan to switch these Brazilian Portuguese notices to English until they can be translated at a later date. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467878 ] Jean T. Anderson commented on DERBY-2237: - Yeah, I just noticed the same thing on another thread. I believe the copyright page that users view should conform to this: http://www.apache.org/dev/apply-license.html But that page is out of date, and I noticed mention of that lately on another list. I'll chase that reference down. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467884 ] Jean T. Anderson commented on DERBY-2237: - The mention that I recalled about apply-license.html being out of date really had to do with the NOTICE file [1], and wasn't resolved from what I could see. At any rate, http://www.apache.org/dev/apply-license.html points to [2], which is what we should be doing on each copyright page the end user sees (updating the 2006 to 2007 where it makes sense): Copyright 2004-2006 The Apache Software Foundation Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Agree? Disagree? [1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200610.mbox/[EMAIL PROTECTED] [2] http://www.apache.org/licenses/LICENSE-2.0.html#apply Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467888 ] Jean T. Anderson commented on DERBY-2237: - I believe that these Brazilian Portuguese copyright pages: https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/pt_BR/adminguide/radmincopyright.dita https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/pt_BR/getstart/rgscopyright.dita https://svn.apache.org/repos/asf/db/derby/docs/trunk/src/pt_BR/ref/rrefcopyright.dita only need a change of the Copyright line from this: Copyright 1997, 2005 Apache Software Foundation, ou seus concessores de licença, conforme se aplique. to this: Copyright 2004-2006 The Apache Software Foundation From my knowledge of Spanish, it looks to me like the text below that is a translation of http://www.apache.org/licenses/LICENSE-2.0.html#apply -- so it's correct. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2275) XSLT changes for PDF output
[ https://issues.apache.org/jira/browse/DERBY-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467932 ] Jean T. Anderson commented on DERBY-2275: - I tested header2.patch and the resulting pdf's look good. Regarding the Version 10 vs. Version 10.2 tag that gets output, the version gets set in the vrmlist variables of each book's ditamap. Scott posted details at: http://mail-archives.apache.org/mod_mbox/db-derby-dev/200701.mbox/[EMAIL PROTECTED] I also did an 'ant all' to verify that changes to the lib/dita2fo-shell.xsl still result in a successful build. But I don't know DITA markup. If anybody who knows DITA has time to check this patch, that'd be great. XSLT changes for PDF output --- Key: DERBY-2275 URL: https://issues.apache.org/jira/browse/DERBY-2275 Project: Derby Issue Type: Improvement Components: Documentation Environment: any Reporter: scott hutinger Priority: Minor Attachments: header1.patch.gz, header2.patch.gz patch for dita2fo-shell.xsl - adds copyright to title page - header is now the document title instead of Copyright - Table of contents header has derby version and name of document on the header -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2275) XSLT changes for PDF output
[ https://issues.apache.org/jira/browse/DERBY-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson resolved DERBY-2275. - Resolution: Fixed Fix Version/s: 10.3.0.0 Derby Info: (was: [Patch Available]) Committed to the trunk revision 500385. Thanks for the contribution, Scott! XSLT changes for PDF output --- Key: DERBY-2275 URL: https://issues.apache.org/jira/browse/DERBY-2275 Project: Derby Issue Type: Improvement Components: Documentation Environment: any Reporter: scott hutinger Priority: Minor Fix For: 10.3.0.0 Attachments: header1.patch.gz, header2.patch.gz patch for dita2fo-shell.xsl - adds copyright to title page - header is now the document title instead of Copyright - Table of contents header has derby version and name of document on the header -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467962 ] Jean T. Anderson commented on DERBY-2237: - I understand your point about the this file reference, but the HTTPD project, which seems to be the de facto model for other projects uses it. I downloaded httpd-docs-2.2.2.en.pdf and it has a section at the beginning that clarifies it with the title About the PDF Documentation on page 2: Copyright (c) 2005 The Apache Software Foundation Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. I think the context for this file is this file comprising the documentation. The pdf also includes the text for the Apache License in its entirety starting on page 9 in the Release Notes chapter. Online docs follow a similar format: http://httpd.apache.org/docs/2.2/license.html Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467966 ] Jean T. Anderson commented on DERBY-2237: - Incidently, at the bottom of each HTTP online doc page, there is this: Copyright 2006 The Apache Software Foundation. Licensed under the Apache License, Version 2.0. The second line links to http://www.apache.org/licenses/LICENSE-2.0 . For example, see: http://httpd.apache.org/docs/trunk/mod/mod_speling.html Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2227) Web Site - Add Checklist page for Doc updates for each release
[ https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466571 ] Jean T. Anderson commented on DERBY-2227: - I think licencing should be licensing. Are these missing closing quotes? copyryear year=2002,2006 copyryear year=2002,2007 It might be helpful to add a link to http://wiki.apache.org/db-derby/DerbySnapshotOrRelease as the higher level writeup on what needs to be done for releases. Web Site - Add Checklist page for Doc updates for each release -- Key: DERBY-2227 URL: https://issues.apache.org/jira/browse/DERBY-2227 Project: Derby Issue Type: Improvement Components: Web Site Reporter: Laura Stewart Assigned To: Laura Stewart Priority: Minor Attachments: Derby2227-1.diff, derby2227-1.zip, docscheck.html, site.xml Create a list of items to check and update for each release for the documentation. This list should include copywrite info, dates/time issues in the Working with Derby See this thread: http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2255) ij should indicate that it is waiting for more input in a multi-line interactive statement.
[ https://issues.apache.org/jira/browse/DERBY-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466188 ] Jean T. Anderson commented on DERBY-2255: - This worked fine for me on max osx (10.4). It doesn't catch a carriage return inside a quote (and I'd argue it really shouldn't because a carriage return could be part of the data). For example, here's a query with a properly closed quote: ij select * from bar where description = 'here is row 2'; ID |DESCRIPTION 2 |here is row 2 1 row selected And here's a query without a close quote before the semicolon: ij select * from bar where description='here is row 3; === hangs here with no continuation prompt === I think users might still be confused -- but hopefully less confused because they can see the continuation prompt on the preceding lines. ij should indicate that it is waiting for more input in a multi-line interactive statement. --- Key: DERBY-2255 URL: https://issues.apache.org/jira/browse/DERBY-2255 Project: Derby Issue Type: Improvement Components: Tools Affects Versions: 10.2.2.0 Reporter: Anders Morken Assigned To: Anders Morken Priority: Trivial Attachments: DERBY-2255-1.diff, DERBY-2255-2.diff Many users have been confused by the lack of response from ij when they forget to end a statement with a semicolon, and believe that Derby is taking its sweet time answering their query, while ij is simply waiting for more input. This issue tries to address this by adding a short prompt to the next line after a newline has been entered by the user without ending the statement with a semicolon. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1842) Accessibility of figures in Derby Docs
[ https://issues.apache.org/jira/browse/DERBY-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465619 ] Jean T. Anderson commented on DERBY-1842: - Regarding: 1) The Alternate text does not pop up at all using my installation of FireFox (5.0; en-US; rv:1.8.0.9) but it works as advertised in IE. ALT text won't display on mouse-over using Firefox or Safari -- the HTML standard doesn't require a browser to display ALT text unless the image can't be rendered. See the derby-dev topic starting at http://mail-archives.apache.org/mod_mbox/db-derby-dev/200701.mbox/[EMAIL PROTECTED] Accessibility of figures in Derby Docs -- Key: DERBY-1842 URL: https://issues.apache.org/jira/browse/DERBY-1842 Project: Derby Issue Type: Improvement Components: Documentation Affects Versions: 10.2.1.6 Reporter: Laura Stewart Assigned To: Laura Stewart Attachments: derby1842_1.diff, derby1842_html.zip All of the figures in the Derby documentation do have alternative text which enables people with disabilities to interpret the figures with screen readers. There is one figure in file cdevdeploy855655 where the figure description is so poor as to be useless. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2134) Add long running System test for Derby
[ https://issues.apache.org/jira/browse/DERBY-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464999 ] Jean T. Anderson commented on DERBY-2134: - This code is cleared for import. Incubator notice: http://mail-archives.apache.org/mod_mbox/incubator-general/200701.mbox/[EMAIL PROTECTED] Result: http://www.nabble.com/-RESULT--IP-CLEARANCE--IBM-contribution-to-Apache-Derby-p8380114.html Add long running System test for Derby -- Key: DERBY-2134 URL: https://issues.apache.org/jira/browse/DERBY-2134 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.2.1.6 Reporter: Manjula Kutty Assigned To: Manjula Kutty Fix For: 10.2.3.0 Attachments: Scenario.zip, Sttest.zip I will use this place to add 2 long running system tests for Derby. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2227) Web Site - Add Checklist page for Doc updates for each release
[ https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464251 ] Jean T. Anderson commented on DERBY-2227: - Here's more clarification because this can be kind of confusing We need to separate the issues of source from built product because the ASF requirements are different. The ASF source header policy [1] requires that a source file NOT have a copyright statement in it; it should have the header specified in [1]. There was a flurry of activity before 10.2.1.6 was released to update derby source (DERBY-1377, DERBY-1422). The copyright goes into the NOTICE file instead. The answer for [1]'s FAQ What if my project includes its web site within a product distribution? covers all documentation (not just web site): Documentation, including web site documentation distributed with the release, may include the header text within some form of metadata (such as HTML comments) or as a header or footer appearing in the visible documentation. So that's the *source file* policy. For the built and distributed product, things aren't quite so cut and dried from my read. Look at the FAQ for [1]: Does this policy also apply to content displayed on our web sites? The answer is currently no. At some point, a terms of use link might be added to web site pges. ASF guidelines for how to form the copyright statement are covered in [2]. I don't think that a copyright needs to appear on each displayed page, but that discussion might be better moved to DERBY-2237. [1] http://www.apache.org/legal/src-headers.html [2] http://www.apache.org/dev/apply-license.html Web Site - Add Checklist page for Doc updates for each release -- Key: DERBY-2227 URL: https://issues.apache.org/jira/browse/DERBY-2227 Project: Derby Issue Type: Improvement Components: Web Site Reporter: Laura Stewart Assigned To: Laura Stewart Priority: Minor Attachments: docscheck.html, site.xml Create a list of items to check and update for each release for the documentation. This list should include copywrite info, dates/time issues in the Working with Derby See this thread: http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2227) Web Site - Add Checklist page for Doc updates for each release
[ https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464256 ] Jean T. Anderson commented on DERBY-2227: - And one MORE clarification. :-) Where I wrote: The ASF source header policy [1] requires that a source file NOT have a copyright statement in it; I meant that the source file must not have an *ASF* copyright statement (the ASF copyright belongs in the NOTICE file). It's possible for a source file to have have non-ASF copyright statements in it. Lots of details are in [1]. [1] http://www.apache.org/legal/src-headers.html Web Site - Add Checklist page for Doc updates for each release -- Key: DERBY-2227 URL: https://issues.apache.org/jira/browse/DERBY-2227 Project: Derby Issue Type: Improvement Components: Web Site Reporter: Laura Stewart Assigned To: Laura Stewart Priority: Minor Attachments: docscheck.html, site.xml Create a list of items to check and update for each release for the documentation. This list should include copywrite info, dates/time issues in the Working with Derby See this thread: http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2237) adds copyright header in th e form of Copyright©1997, 2005: Apache Software Foundation
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464259 ] Jean T. Anderson commented on DERBY-2237: - Where is the 1997,2005 coming from? --That's incorrect for the ASF product. For all 10.2 books it should be 2004,2006. Would you be willing to modify this issue to be a more general copyright cleanup for the DITA source and generated docs? --I'm spotting other problems and don't want to hijack this issue unless you're willing. adds copyright header in the form of Copyright©1997, 2005: Apache Software Foundation - Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Improvement Components: Documentation Environment: linux Reporter: scott hutinger Priority: Trivial Attachments: dita2fo-shell-copyr1.diff.gz a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2237) Cleanup copyrights in the DITA source and generated docs
[ https://issues.apache.org/jira/browse/DERBY-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean T. Anderson updated DERBY-2237: Description: Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / was:a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. Priority: Blocker (was: Trivial) Urgency: Urgent Affects Version/s: 10.2.1.6 10.2.2.0 Issue Type: Bug (was: Improvement) Summary: Cleanup copyrights in the DITA source and generated docs (was: adds copyright header in the form of Copyright©1997, 2005: Apache Software Foundation) Changing short summary from adds copyright header in the form of Copyright©1997, 2005: Apache Software Foundation to Cleanup copyrights in the DITA source and generated docs. Cleanup copyrights in the DITA source and generated docs Key: DERBY-2237 URL: https://issues.apache.org/jira/browse/DERBY-2237 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6, 10.2.2.0 Environment: linux Reporter: scott hutinger Priority: Blocker Attachments: dita2fo-shell-copyr1.diff.gz Problems include: 1) The PDF docs currently include an empty Copyright string in the header. dita2fo-shell-copyr1.diff.gz is a patch to fix the fop (.pdf) copyright header which is currently blank. This is from march 9, 2006. 2) Some source files have the old style copyright in the header that is not in compliance with http://www.apache.org/legal/src-headers.html. For example, see src/ref/rrefsistabssyscolperms.dita 3) The generated html docs have new copyright tags added, such as these entries in ref/crefjavbclobnot.html meta name=copyright content=(C) Copyright 2005 / meta name=DC.rights.owner content=(C) Copyright 2005 / -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
