[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281216#comment-16281216
]
Rick Hillegas commented on DERBY-6809:
--
Looks like Knut and Bryan have answered your questions
[
https://issues.apache.org/jira/browse/DERBY-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277949#comment-16277949
]
Rick Hillegas commented on DERBY-6972:
--
I think that the root cause is this line near the end
[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277907#comment-16277907
]
Rick Hillegas commented on DERBY-6809:
--
Your screenshot indicates that you have checked out the 10.14
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275776#comment-16275776
]
Rick Hillegas commented on DERBY-6945:
--
Tests passed cleanly on derby-6945-01-aa
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6945:
-
Attachment: derby-6945-01-aa-remove_derbyPreBuild_dep.diff
Attaching derby-6945-01-aa
[
https://issues.apache.org/jira/browse/DERBY-6978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275652#comment-16275652
]
Rick Hillegas commented on DERBY-6978:
--
Hi Christian,
I can confirm that you are not going crazy
[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275164#comment-16275164
]
Rick Hillegas commented on DERBY-6809:
--
Q> Do you think that rewriting code with new enhanceme
[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6979:
-
Bug behavior facts: Seen in production (was: Performance)
> Derby is still in read-only m
[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6979:
-
Issue Type: Improvement (was: Bug)
> Derby is still in read-only mode，even through I
[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6979:
-
Component/s: Store
> Derby is still in read-only mode，even through I had released the disk sp
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273885#comment-16273885
]
Rick Hillegas commented on DERBY-6945:
--
Alex Buckley in the Oracle Java group makes the following
[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273660#comment-16273660
]
Rick Hillegas commented on DERBY-6809:
--
Q> Also, does derby still compile to Java 6 bytecode or
[
https://issues.apache.org/jira/browse/DERBY-6978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271830#comment-16271830
]
Rick Hillegas commented on DERBY-6978:
--
Could you attach the database in a more standard format
[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271812#comment-16271812
]
Rick Hillegas commented on DERBY-6979:
--
I have never seen this problem before. Have you tried
[
https://issues.apache.org/jira/browse/DERBY-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6979:
-
Bug behavior facts: Performance (was: Deviation from standard,Performance)
> Derby is st
[
https://issues.apache.org/jira/browse/DERBY-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16271745#comment-16271745
]
Rick Hillegas commented on DERBY-6809:
--
Note that the next feature release (10.15) will be targetted
My last comment on https://issues.apache.org/jira/browse/DERBY-6945
proposes how we could decompose Derby into Jigsaw-ready modules. Mostly,
these correspond to the existing release jars. However, one additional
module (and jar file) is proposed; it corresponds to the code currently
shared
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265882#comment-16265882
]
Rick Hillegas edited comment on DERBY-6945 at 11/25/17 11:50 PM:
-
Here
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6945:
-
Attachment: jdeps.out.tar
Here are my initial thoughts about dividing Derby 10.15 into Jigsaw
On 11/23/17 3:39 AM, Knut Anders Hatlen wrote:
Knut Anders Hatlen <knut.hat...@oracle.com> writes:
Rick Hillegas <rick.hille...@gmail.com> writes:
On 11/22/17 12:56 AM, Knut Anders Hatlen wrote:
Rick Hillegas <rick.hille...@gmail.com> writes:
I have updated the
[
https://issues.apache.org/jira/browse/DERBY-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265474#comment-16265474
]
Rick Hillegas commented on DERBY-4842:
--
There is also the CREATE OR REPLACE syntax, which
On 11/22/17 12:56 AM, Knut Anders Hatlen wrote:
Rick Hillegas <rick.hille...@gmail.com> writes:
I have updated the Derby-trunk-JaCoCo configuration to use the 0.7.9
JaCoCo jars at
https://urldefense.proofpoint.com/v2/url?u=http-3A__people.apache.org_-7Erhillegas_derby_jacoco-2Djars_=
[
https://issues.apache.org/jira/browse/DERBY-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263798#comment-16263798
]
Rick Hillegas commented on DERBY-6975:
--
Hey David,
I'm sorry for my tardy response. I did not see
? See
https://builds.apache.org/view/All/job/Derby-JaCoCo/configure
and
https://builds.apache.org/view/All/job/Derby-trunk-JaCoCo/configure
Thanks,
-Rick
On 11/7/17 4:19 PM, Rick Hillegas wrote:
On 11/6/17 5:06 PM, Rick Hillegas wrote:
On 11/5/17 7:36 PM, Bryan Pendleton wrote:
Here, I see
On 11/17/17 6:37 PM, Bryan Pendleton wrote:
Afer that worked, I replaced "jdbc:derby:memory:db" with
"jdbc:derby://localhost:1527/demo4" and got the exception I'm pasting below
this. I don´t know what I'm configuring wrong.
Exception in thread "main" java.sql.SQLSyntaxErrorException:
On 11/16/17 2:34 PM, AlbertoLopez wrote:
I created a database, and need to convert it to NATIVE authentication.
Derby's Developer's Manual states I need to create an user in order to
conver it. I tried to do that and get a "procedure not recognized"
exception.
I viewed the SYSCS_UTIL folder,
Any theories about why the following tests failed with security
exceptions during a recent Jenkins run? They succeed on my laptop:
org.apache.derbyTesting.functionTests.tests.derbynet.ProtocolTest
org.apache.derbyTesting.functionTests.tests.jdbcapi.InternationalConnectSimpleDSTest
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253443#comment-16253443
]
Rick Hillegas commented on DERBY-6974:
--
Tests passed cleanly for me on derby-6974-02-ab-minVersion9
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6974:
-
Attachment: derby-6974-02-ab-minVersion9.diff
Attaching derby-6974-02-ab-minVersion9.diff
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16252773#comment-16252773
]
Rick Hillegas commented on DERBY-6974:
--
Hey Bryan,
The min.version variable is used to set
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6974:
-
Attachment: derby-6974-02-minVersion1.9.diff
Attaching derby-6974-01-ab-deprecateJDK8.diff
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16250582#comment-16250582
]
Rick Hillegas commented on DERBY-6977:
--
Tests passed cleanly for me on derby-6977-01-ad-useUUID.diff
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6977:
-
Attachment: derby-6977-01-ad-useUUID.diff
Attaching SUBMISSIONS/derby-6977-01-ad-useUUID.diff
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6977:
-
Attachment: derby-6977-01-ac-useUUID.diff
Attaching derby-6977-01-ac-useUUID.diff. This patch
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248994#comment-16248994
]
Rick Hillegas commented on DERBY-6977:
--
I believe that I have discovered the reason
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248956#comment-16248956
]
Rick Hillegas commented on DERBY-6974:
--
tools/ant/properties/defaultcompiler.properties still needs
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6977:
-
Attachment: derby-6977-01-ab-useUUID.diff
Attaching derby-6977-01-ab-useUUID.diff. This patch
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248638#comment-16248638
]
Rick Hillegas commented on DERBY-6977:
--
No, that wouldn't help. The stringified UUID by itself
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248558#comment-16248558
]
Rick Hillegas commented on DERBY-6977:
--
Thanks for the feedback, Bryan and Trejkaz. To answer Bryan's
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6977:
-
Attachment: derby-6977-01-aa-useUUID.diff
Attaching derby-6977-01-aa-useUUID.diff. This patch
[
https://issues.apache.org/jira/browse/DERBY-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247866#comment-16247866
]
Rick Hillegas commented on DERBY-6977:
--
The value is being generated by some convoluted, bogus
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas closed DERBY-5543.
> include debug info in derby builds uploaded to ma
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas resolved DERBY-5543.
--
Resolution: Fixed
Fix Version/s: 10.15.0.0
Resolving. I believe work on this issue
On 11/6/17 5:06 PM, Rick Hillegas wrote:
On 11/5/17 7:36 PM, Bryan Pendleton wrote:
Here, I see that to support Java 9, we need JaCoCo 0.7.8:
https://groups.google.com/forum/#!msg/jacoco/Zf0Cwj13G2g/wpyrYAEECAAJ
If I understand that script, our JaCoCo runs rely on an old JaCoCo
version
cached
On 11/5/17 7:36 PM, Bryan Pendleton wrote:
Here, I see that to support Java 9, we need JaCoCo 0.7.8:
https://groups.google.com/forum/#!msg/jacoco/Zf0Cwj13G2g/wpyrYAEECAAJ
If I understand that script, our JaCoCo runs rely on an old JaCoCo version
cached on Kristian's Apache website. Here are
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5543:
-
Attachment: derby-5543-01-ab-insaneWithLineNumbers.diff
Attaching derby-5543-01-ab
On 11/5/17 9:08 AM, Bryan Pendleton wrote:
The Derby-Trunk build seemed to work OK (Rick can you verify?) so I
made the corresponding change to the Derby-trunk-suites.All and
Derby-trunk-JaCoCo jobs and submitted them, too:
Thanks for digging into this, Bryan. More inline...
On 11/5/17 10:46 AM, Bryan Pendleton wrote:
https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-JaCoCo/49/
This build correctly used Java 9.
But it did not run successfully.
I filed https://issues.apache.org/jira/browse/DERBY-6976
On 11/5/17 8:38 AM, Bryan Pendleton wrote:
Hi Rick,
I found a drop list in the "configure" screen under "General" where I
could pick a JDK, and I picked "JDK 1.9 latest".
Great. I was looking on the Build and Build Environment tabs.
Thanks,
-Rick
I ran another build:
I don't seem to know how to configure the Jenkins trunk build to use
Java 9. I tried adjusting the Tool Environment section, but that had no
effect. In the Build Environment tab I see a dropdown for specifying the
Ant version. But I don't see a dropdown for specifying the JDK version.
My
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239587#comment-16239587
]
Rick Hillegas commented on DERBY-2212:
--
Thanks!
> Add "Unique where not null" to
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238634#comment-16238634
]
Rick Hillegas commented on DERBY-2212:
--
Yes, a unique constraint can be added after a table
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16237007#comment-16237007
]
Rick Hillegas commented on DERBY-2212:
--
Right. The unique index treats NULL as a distinct, known
[
https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235031#comment-16235031
]
Rick Hillegas commented on DERBY-2212:
--
Can you describe your use case which is not satisfied
A long time ago, Kristian proposed that we compile the insane,
production jars with line number information, but not full debug
information. The idea would be to get more information out of production
stack traces at the cost of increasing the size of the jar files. Users
have renewed this
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233563#comment-16233563
]
Rick Hillegas commented on DERBY-5543:
--
When I compile the engine with these attributes set
[
https://issues.apache.org/jira/browse/DERBY-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16232597#comment-16232597
]
Rick Hillegas commented on DERBY-6975:
--
Thanks for describing your experience, David. A couple
On 10/29/17 6:49 PM, Bryan Pendleton wrote:
Hi Rick,
What do we need to do with our Apache-hosted Jenkins build runs?
Presumably, the Jenkins builds of main should use Java 9.
The Jenkins builds of older branches should use the appropriate Java version.
Have you already taken care of this?
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5543:
-
Urgency: Urgent (was: Low)
> include debug info in derby builds uploaded to ma
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226739#comment-16226739
]
Rick Hillegas commented on DERBY-5543:
--
I have assigned this bug to myself. I think that line numbers
[
https://issues.apache.org/jira/browse/DERBY-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas reassigned DERBY-5543:
Assignee: Rick Hillegas
> include debug info in derby builds uploaded to ma
On 10/29/17 6:49 PM, Bryan Pendleton wrote:
Hi Rick,
What do we need to do with our Apache-hosted Jenkins build runs?
Presumably, the Jenkins builds of main should use Java 9.
The Jenkins builds of older branches should use the appropriate Java version.
Have you already taken care of this?
My last checkin (derby-6974-01-ab-deprecateJDK8.diff, svn 1813709)
converted the Derby build so that Derby can only be compiled into Java 9
byte code. The trunk no longer runs on older JVMs.
Automated continuous integration rigs will need to disable test cycles
involving the development trunk
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224203#comment-16224203
]
Rick Hillegas commented on DERBY-6974:
--
Tests ran cleanly on derby-6974-01-ab-deprecateJDK8.diff
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6974:
-
Attachment: derby-6974-01-ab-deprecateJDK8.diff
Attaching derby-6974-01-ab-deprecateJDK8.diff
[
https://issues.apache.org/jira/browse/DERBY-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6974:
-
Attachment: derby-6974-01-aa-deprecateJDK8.diff
Attaching derby-6974-01-aa-deprecateJDK8.diff
Hi Bryan,
Some responses inline...
On 10/23/17 8:02 PM, Bryan Pendleton wrote:
Let me know if I should hold off doing this. Once I check in the changes,
you will no longer be able to use JDK 8 in order to build Derby. Instead,
Hi Rick, two clarifying questions:
1) This will only affect the
I am ready to begin the task of deprecating support for JDK 8 and
converting the Derby build to use JDK 9 instead, as agreed by the
community last July:
http://apache-database.10148.n7.nabble.com/RESULT-VOTE-Sunsetting-support-for-Java-8-td147735.html.
Let me know if I should hold off doing
Rick Hillegas created DERBY-6974:
Summary: Deprecate support for building Derby under JDK 8
Key: DERBY-6974
URL: https://issues.apache.org/jira/browse/DERBY-6974
Project: Derby
Issue Type
[
https://issues.apache.org/jira/browse/DERBY-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216176#comment-16216176
]
Rick Hillegas commented on DERBY-6972:
--
The server raises this error when it receives a garbled DRDA
[
https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216166#comment-16216166
]
Rick Hillegas commented on DERBY-6973:
--
I have left this issue as Urgent and added 10.15.0.0
[
https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6973:
-
Affects Version/s: 10.15.0.0
> Provide SHA-512 checksums on future relea
[
https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216164#comment-16216164
]
Rick Hillegas commented on DERBY-6973:
--
MD5 is a checksum type used by the following other popular
[
https://issues.apache.org/jira/browse/DERBY-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6973:
-
Summary: Provide SHA-512 checksums on future releases (was: md5 given in
dowload artifacts
I think that I am done with the tasks for publishing 10.14.1.0. Let me
know if you notice something awry.
Thanks,
-Rick
https://blogs.apache.org/infra/entry/committer_shell_access_to_people
http://linux.die.net/man/1/ssh-add
http://linux.die.net/man/1/ssh-agent
Craig
On Oct 21, 2017, at 11:05 AM, Rick Hillegas <rick.hille...@gmail.com
<mailto:rick.hille...@gmail.com>> wrote:
Dear announce-owner
[
https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6970:
-
Attachment: DERBY_6970.java
The Derby DataSource implementations conform to the JDBC standard
Subject:Cannot post a release announcement to announce@
Date: Sat, 21 Oct 2017 08:46:53 -0700
From: Rick Hillegas <rick.hille...@gmail.com>
To: announce-h...@apache.org, derby-dev@db.apache.org
<derby-dev@db.apache.org>
Dear announce-help,
I hope that someone
Dear announce-help,
I hope that someone will be able to help me with the following problem:
I am trying to publish a new release of Apache Derby
(http://db.apache.org/derby/releases/release-10.14.1.0.cgi). I have
successfully sent the release announcement to our user and developer
lists.
The Apache Derby project is pleased to announce feature release 10.14.1.0.
Apache Derby is a sub-project of the Apache DB project. Derby is a pure
Java relational database engine which conforms to the ISO/ANSI SQL and
JDBC standards. Derby aims to be easy for developers and end-users to
work
On 10/16/17 8:01 PM, Bryan Pendleton wrote:
I see the same behavior, Rick.
I don't immediately see what's wrong.
That entire mirror distribution system is pretty opaque to me.
Perhaps you should ping infra@ ?
bryan
I'm getting closer to being able to announce the 10.14.1.0 release. The
[
https://issues.apache.org/jira/browse/DERBY-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208692#comment-16208692
]
Rick Hillegas edited comment on DERBY-6971 at 10/18/17 1:40 AM:
Thanks
[
https://issues.apache.org/jira/browse/DERBY-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16208692#comment-16208692
]
Rick Hillegas commented on DERBY-6971:
--
Thanks for those pointers. The following MySQL-inspired
[
https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206918#comment-16206918
]
Rick Hillegas commented on DERBY-6970:
--
See the attached DERBY_6970 program for an example of how
[
https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6970:
-
Attachment: DERBY_6970.java
Attaching DERBY_6970.java. This is a test program which demonstrates
[
https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6970:
-
Urgency: Low (was: Urgent)
> No support for setting connection timeout for a connect
I've never tripped across this problem before. I pushed 10.14.1.0 to the
distribution site on Saturday and I can see the artifacts here:
https://dist.apache.org/repos/dist/release/db/derby/db-derby-10.14.1.0/
But I can't select a mirror from the download page at
[
https://issues.apache.org/jira/browse/DERBY-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16206879#comment-16206879
]
Rick Hillegas commented on DERBY-6971:
--
Can you elaborate? This topic was raised on the developer's
On 10/16/17 4:46 AM, Bryan Pendleton wrote:
The release announcement looks great!
I don't recall the details of how (or even if) I posted to announce@
for 10.13. Did you happen to search the archives to see if a mail from
me went out during that release, and, if so, which account I used to
send
Here is a first draft of a release announcement for 10.14.1.0. Please
let me know how I can improve this.
Also, I need a little advice. In the past, I had to ssh to my Apache
account in order to post a release announcement to annou...@apache.org.
We can no longer ssh to the Apache machines.
[
https://issues.apache.org/jira/browse/DERBY-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16202854#comment-16202854
]
Rick Hillegas commented on DERBY-6945:
--
I see the following major steps to this effort.
1) Deprecate
Thanks for everyone's work on coding, documenting, and testing
10.14.1.0. The polls have closed. The community has approved 10.14.1.0
as an official Derby release:
+1:
Bryan Pendleton (pmc)
Kim Haase (pmc)
Rick Hillegas (pmc)
No other votes were cast.
Rick Hillegas created DERBY-6969:
Summary: Results from DatabaseMetaData.getBestRowIdentifier() need
to be sorted
Key: DERBY-6969
URL: https://issues.apache.org/jira/browse/DERBY-6969
Project: Derby
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196344#comment-16196344
]
Rick Hillegas commented on DERBY-6968:
--
Thanks for the quick review, Bryan. Tests passed cleanly
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6968:
-
Attachment: derby-6968-01-aa-assertUnorderedResultSet.diff
Attaching derby-6968-01-aa
. That
error appears to be a test instability and not a regression in product
behavior.
I am satisfied with 10.14.1.0.
+1
-Rick
On 9/20/17 5:42 AM, Rick Hillegas wrote:
Please test-drive the 10.14.1.0 candidate, then vote on whether to
accept it as a Derby release. The candidate lives at:
http
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196273#comment-16196273
]
Rick Hillegas commented on DERBY-6968:
--
Hey Bryan,
Thanks for pointing out the ordering on the SCOPE
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6968:
-
Attachment: 10.14.1.testResults.0-failures
Attaching 10.14.1.testResults.0-failures, a survey
[
https://issues.apache.org/jira/browse/DERBY-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-6968:
-
Affects Version/s: 10.14.1.0
> Instability in DatabaseMetaDataTest.testGetBestRowIdentif
Rick Hillegas created DERBY-6968:
Summary: Instability in
DatabaseMetaDataTest.testGetBestRowIdentifier
Key: DERBY-6968
URL: https://issues.apache.org/jira/browse/DERBY-6968
Project: Derby
901 - 1000 of 11789 matches
Mail list logo
