[
https://issues.apache.org/jira/browse/DERBY-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577466#comment-13577466
]
Knut Anders Hatlen commented on DERBY-3398:
---
In the cases where we don't have a
[
https://issues.apache.org/jira/browse/DERBY-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577474#comment-13577474
]
Kristian Waagan commented on DERBY-3398:
I talked briefly to Dag on this topic,
[
https://issues.apache.org/jira/browse/DERBY-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577485#comment-13577485
]
Knut Anders Hatlen commented on DERBY-3398:
---
One could also imagine the
Christian Müller created DERBY-6069:
---
Summary: Derby doesn't export the version number in its OSGI
exported packages
Key: DERBY-6069
URL: https://issues.apache.org/jira/browse/DERBY-6069
Project:
[
https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6000:
-
Attachment: derby-6000-17-aa-getMaxLogicalLobSize.diff
Attaching
[
https://issues.apache.org/jira/browse/DERBY-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6000:
-
Attachment: JDBC_4.2_Changes.html
Attaching a revised version of the functional spec. This
[
https://issues.apache.org/jira/browse/DERBY-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577575#comment-13577575
]
Kim Haase commented on DERBY-6059:
--
Thanks for catching that, Dag, and for the careful
[
https://issues.apache.org/jira/browse/DERBY-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577581#comment-13577581
]
Kim Haase commented on DERBY-6061:
--
Thanks, Dag. Unfortunately both my mailer and browser
Java DB testing and reporting infrastructure.
Success continuous trunk (rev 1445557)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5572447-report/
[
https://issues.apache.org/jira/browse/DERBY-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577672#comment-13577672
]
Kim Haase commented on DERBY-6059:
--
Committed patch DERBY-6059.diff to documentation
Rick Hillegas created DERBY-6070:
Summary: Document Derby's JDBC 4.2 implementation
Key: DERBY-6070
URL: https://issues.apache.org/jira/browse/DERBY-6070
Project: Derby
Issue Type:
[
https://issues.apache.org/jira/browse/DERBY-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6059:
-
Attachment: rrefattribtracelevel.html
DERBY-6059-2.stat
DERBY-6059-2.diff
On Tue, Feb 12, 2013 at 7:37 AM, Rick Hillegas rick.hille...@oracle.com wrote:
Thanks for noticing this, Myrna. As Kristian noted, these warnings are
caused by the fact that the Java 7 javadoc tool can't find new Java 8
classes in java.sql. Those classes are referenced by the JDBC 4.2 support
Java DB testing and reporting infrastructure.
Success continuous trunk (rev 1445591)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5572460-report/
[
https://issues.apache.org/jira/browse/DERBY-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-6059.
--
Resolution: Fixed
Issue fix info: (was: Patch Available)
Committed patch
[
https://issues.apache.org/jira/browse/DERBY-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase reassigned DERBY-6070:
Assignee: Kim Haase
Document Derby's JDBC 4.2 implementation
On 2/13/13 10:11 AM, Myrna van Lunteren wrote:
On Tue, Feb 12, 2013 at 7:37 AM, Rick Hillegasrick.hille...@oracle.com wrote:
Thanks for noticing this, Myrna. As Kristian noted, these warnings are
caused by the fact that the Java 7 javadoc tool can't find new Java 8
classes in java.sql. Those
Java DB testing and reporting infrastructure.
Success win8-test(32bit) trunk (rev 1445030)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5572395-report/
[
https://issues.apache.org/jira/browse/DERBY-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-6045:
--
Issue fix info: High Value Fix
Bug behavior facts: Performance,Regression,Seen in
On 2/13/13 12:50 AM, Atul Agrawal wrote:
Dear Derby Team,
I have forgotten the password for the Derby Database. Can you please
guide if there is any way to reset it or any other way to access the
schema of the database.
I am more concerned about schema then data. please let me know if
On Wed, Feb 13, 2013 at 11:03 AM, Rick Hillegas
rick.hille...@oracle.com wrote:
On 2/13/13 10:11 AM, Myrna van Lunteren wrote:
Hi Rick,
Thanks for fixing the previous warnings. However, now the javadoc
build fails, with the following:
[path_to_trunk]\build.xml:1388: Javadoc failed:
Myrna van Lunteren created DERBY-6071:
-
Summary: trunk javadoc build fails with Javadoc failed:
java.io.IOException: Cannot run program \bin\javadoc.exe: CreateProcess
error=206, The filename or extension is too long.
Key:
[
https://issues.apache.org/jira/browse/DERBY-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578048#comment-13578048
]
Myrna van Lunteren commented on DERBY-6071:
---
committed the change with revision
[
https://issues.apache.org/jira/browse/DERBY-6071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-6071.
---
Resolution: Fixed
Assignee: Myrna van Lunteren
Issue fix info:
Java DB testing and reporting infrastructure.
Success nightly trunk (rev 1445591)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5572486-report/
Java DB testing and reporting infrastructure.
Success win8-test trunk (rev 1445030)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5572392-report/
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5977:
--
Attachment: DERBY-5977_3.diff
DERBY-5977_3.stat
Attaching a patch that
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578092#comment-13578092
]
Myrna van Lunteren edited comment on DERBY-5977 at 2/14/13 1:56 AM:
[
https://issues.apache.org/jira/browse/DERBY-5977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578100#comment-13578100
]
Myrna van Lunteren commented on DERBY-5977:
---
For completeness' sake, the
Java DB testing and reporting infrastructure.
Success continuous trunk (rev 1445994)
No errors or failures.
Test report: http://download.java.net/javadesktop/derby/javadb-5572488-report/
[
https://issues.apache.org/jira/browse/DERBY-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578175#comment-13578175
]
Mamta A. Satoor commented on DERBY-6045:
Made some changes to the junit test and
[
https://issues.apache.org/jira/browse/DERBY-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578183#comment-13578183
]
Mamta A. Satoor commented on DERBY-6045:
I ran the new junit test
Hi,
I was wondering if there is a way to set a database property only for
one test fixture within a junit test with many test fixtures. I
recently added a test fixture xtestDerby6045 in
org.apache.derbyTesting.functionTests.tests.lang.InListMultiProbeTest(I
have purposely named it to start with
33 matches
Mail list logo
