On 3/31/24 7:16 AM, Bryan Pendleton wrote:
Hi all, it is time for our April report to the board.
Could you please send me any information about what the community has
been working on over the last three months, so I can include this in
the report?
thanks,
bryan
Hey Bryan,
Nothing big from
Hey Craig,
At the end of this message, I have attached a program which demonstrates
the behavior of Statement.cancel() in both the Derby embedded and
network drivers. As you can see from the following output, both drivers
raise a java.sql.SQLFeatureNotSupportedException exception. I ran the
Hey Craig,
I don't know how DataNucleus tries to cancel a query.
jdbc.sql.Statement.cancel() is an optional method which some DBMSes
implement but Derby doesn't. The method raises a "Feature not supported"
exception according to
https://db.apache.org/derby/docs/10.17/ref/rrefjdbc40794.html
Thanks for the heads-up, David. Derby found no problems with this
release candidate. See https://issues.apache.org/jira/browse/DERBY-7159
On 2/20/24 12:00 AM, David Delabassee wrote:
Welcome to the latest OpenJDK Quality Outreach update!
The first JDK 22 Release Candidates builds are now
the table
definition.
On Sat, 10 Feb 2024, 23:13 Rick Hillegas, wrote:
I get the following error when I run this DDL:
ERROR 42X93: Table 'ACTIVE_LIST' contains a constraint definition with
column 'STUDENTID' which is not in the table.
On 2/10/24 6:03 AM, John English wrote:
CREATE TABLE a
I get the following error when I run this DDL:
ERROR 42X93: Table 'ACTIVE_LIST' contains a constraint definition with
column 'STUDENTID' which is not in the table.
On 2/10/24 6:03 AM, John English wrote:
CREATE TABLE active_list (
username VARCHAR(15) NOT NULL,
surname
I would need to see your full schema before speculating about why these
statements grab these locks.
On 2/2/24 11:46 AM, John English wrote:
My system recently reported the following:
java.sql.SQLTransactionRollbackException: A lock could not be obtained
due to a deadlock, cycle of locks and
The following information may be helpful:
o Developer Guide material on Derby locking:
https://db.apache.org/derby/docs/10.17/devguide/cdevconcepts30291.html
o Reference Guide material on the SYSCS_DIAG.LOCK_TABLE diagnostic
table:
d just before the failed COMMIT) returns the following result:
ij> SELECT talent_id FROM talent WHERE talent_id NOT IN (SELECT
talent_id FROM talentphoto);
TALENT_ID
---
0
1
2
It appears that you need to fix your data.
Hope this helps,
-Rick
On 1/31/24 1:06 PM, Bart van der Bilt wro
On 1/30/24 12:52 PM, jazz wrote:
Hi,
It would be great if this issue could be implemented, I have a use
case for testing. How do I get access to JIRA to update the ticket?
(to include the sql files for testing).
You can request a JIRA account here:
Producing an official Derby release involves a lot of checkins to the
Subversion-controlled source code. Only committers have the ability to
checkin source code.
What you could do is build an unofficial set of jars, sign them, and
post them on a public artifactory.
-Rick
On 1/28/24 8:29
Thanks, David. Derby found no problems with build 22-ea+33-2356. See
https://issues.apache.org/jira/browse/DERBY-7159
On 1/26/24 3:11 AM, David Delabassee wrote:
Greetings!
We are starting 2024 with JDK 22 as it has just entered Rampdown Phase 2 [1].
And with the initial JDK 22 Release
I added a 10.17.1.0 entry to doap_Derby.rdf at the root of the Derby
website source on 2023-11-10 with the derby-7157-13-aa-updateDOAP.diff
patch. 10.17.1.0 is the first release listed in that file. I seem to
recall that it takes a while for information in doap descriptors to
propagate across
Nothing from me. Thanks.
On 1/1/24 3:51 PM, Bryan Pendleton wrote:
Hi all, it is time for our January report to the board.
Could you please send me any information about what the community has
been working on over the last three months, so I can include them in
the report?
Two things I
Thanks, David. Derby has found no problems with build 22-ea+27-2262. See
https://issues.apache.org/jira/browse/DERBY-7159
On 12/13/23 6:08 AM, David Delabassee wrote:
Welcome to the final OpenJDK Quality Outreach update of 2023!
JDK 22, scheduled for General Availability on March 19, 2024, is
but not for this particular need.
Moving to using Procedures for rights seems off the path of feasibly
solving the need to intercepting DML statements to control column values
the application needs.
Thanks for trying to help, it is very much appreciated,
Steve
On Fri, Dec 1, 2023 at 1:42 PM Rick Hillegas
wrote
for your help,
Steve
On Wed, Nov 29, 2023 at 12:35 PM Rick Hillegas
wrote:
You could replace the INSERT trigger with a generated column. I don't see
how to eliminate the UPDATE trigger and preserve the behavior you want.
Here's how to eliminate the INSERT trigger. First make the following class
,
-Steve
On Tue, Nov 28, 2023 at 6:33 PM Rick Hillegas
wrote:
Hi Steven,
Derby hews fairly closely to SQL Standard syntax. Your triggers look wrong
to me. Your triggered SQL statements are VALUES statements, which simply
manufacture some values and throw them into the void. I think that is why
you
Hi Steven,
Derby hews fairly closely to SQL Standard syntax. Your triggers look
wrong to me. Your triggered SQL statements are VALUES statements, which
simply manufacture some values and throw them into the void. I think
that is why you had to include MODE DB2SQL in your syntax. I don't think
on the announce list from you. Did you try that
link I sent?
On Tue, Nov 14, 2023 at 11:11 AM Rick Hillegas wrote:
Thanks, Bryan. I have re-tried sending the announcement, this time
setting my from address to my gmail acccount (which is the forwarding
account for my apache email account
you see the email which I sent to derby-dev,
derby-user, and general@db?
On 11/13/23 5:18 PM, Bryan Pendleton wrote:
Nope, didn't see either one.
bryan
On Mon, Nov 13, 2023 at 4:27 PM Rick Hillegas wrote:
This morning, I sent an announcement message for the 10.17.1.0 release
to annou
The Apache Derby project is pleased to announce feature release 10.17.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
The Apache Derby project is pleased to announce feature release 10.17.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
The Apache Derby project is pleased to announce feature release 10.17.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
This morning, I sent an announcement message for the 10.17.1.0 release
to annou...@apache.org and another announcement message to derby-dev,
derby-user, and general@db. I have not seen either of these messages in
my inboxes. Has anyone else seen these messages?
Thanks,
-Rick
On 11/10/23 12:11 PM, Bryan Pendleton wrote:
Derby 10.17.1.0 has been built and tested on the
Java SE 21 platform, and will run only on Java SE 21 and newer Java
platforms. Derby 10.17.1.0 cannot be used with older Java platforms.
Please seehttp://db.apache.org/derby/derby_downloads.html for
Here is a first draft. Please let me know how to improve it.
---
The Apache Derby project is pleased to announce feature release 10.17.1.0.
Apache Derby is a sub-project of the Apache DB project. Derby is a pure
Java relational database engine which conforms to
I think that I have fixed this problem by adding the following stanza to
the maven war plugin descriptor:
false
On 11/9/23 2:46 PM, Rick Hillegas wrote:
I am trying to install a Derby release into my local maven repository.
The world has changed underneath me in the last
I am trying to install a Derby release into my local maven repository.
The world has changed underneath me in the last year and a half since I
published the last Derby release. The Derby maven-based publication poms
can be found under
Thanks for everyone's work on coding, documenting, and testing
10.17.1.0. The polls have closed. The community has approved 10.17.1.0
as an official Derby release:
+1:
Bryan Pendleton (pmc)
Knut Anders Hatlen (pmc)
Rick Hillegas (pmc)
No other votes were cast.
can be built from the source distro.
+1
On 10/22/23 4:11 PM, Rick Hillegas wrote:
Please test-drive the 10.17.1.0 candidate, then vote on whether to
accept it as a Derby release. The candidate lives at:
https://dist.apache.org/repos/dist/dev/db/derby/db-derby-10.17.1.0/
The polls close at 5
testing with
both Windows 10 and Windows 11.
Thanks for getting the RC together so quickly, Rick!
bryan
On Mon, Oct 9, 2023 at 1:05 PM Rick Hillegas wrote:
I volunteer to be release manager for 10.17.1. I have posted a schedule
for this release:
https://cwiki.apache.org/confluence/display/DERBY
Please test-drive the 10.17.1.0 candidate, then vote on whether to
accept it as a Derby release. The candidate lives at:
https://dist.apache.org/repos/dist/dev/db/derby/db-derby-10.17.1.0/
The polls close at 5:00 pm California time on Monday November 6.
10.17.1.0 is a feature release,
Thanks, Jaikiran and Don. Ant 1.10.14 gets me over this hurdle. I'll let
you know if I encounter other issues building the next Derby release
with Java 21 and this version of Ant. Cheers
On 10/21/23 7:32 AM, Brutzman, Donald (Don) (CIV) wrote:
As Indicated in the email thread, have gotten
I am running Java 21 (OpenJDK 64-Bit Server VM (build 21+35-2513, mixed
mode, sharing)) and Ant 1.10.6. The following stanza in my build.xml
file raises a java.lang.UnsupportedOperationException:
The maintversion2props class is very simple, it just writes
Character data is always stored and retrieved with UTF8 encoding. If you
move your database from a Windows to a Linux platform, the character
encoding will remain UTF8 and everything should work. This assumes that
you are using character-based methods
See https://svn.apache.org/repos/asf/db/derby/code/trunk/RELEASE-NOTES.html
by
2023-11-10.
Thanks to everyone who has volunteered to vet this release.
-Rick
On 10/2/23 9:46 AM, Rick Hillegas wrote:
Our last release is dated May 2022. Would anyone be willing to vet a
new release if I produce it? The key features would be support for the
new LTS version of Java (Java
Thanks, Bryan. I'll see if I can scare up one of our alumnae to help vet
the release.
On 10/2/23 7:49 PM, Bryan Pendleton wrote:
I can definitely be a tester!
I have access to both Windows 10 and to Linux (Ubuntu 20.04) environments.
bryan
On Mon, Oct 2, 2023 at 9:46 AM Rick Hillegas wrote
Our last release is dated May 2022. Would anyone be willing to vet a new
release if I produce it? The key features would be support for the new
LTS version of Java (Java 21) plus a security fix we worked on earlier
this year.
Thanks,
-Rick
he network server, with derby,properties that is
derby.authentication.provider=NATIVE:credentials
the valid users that can create a new db are the one defined in the
credentials db, right?
Thanks for the help.
- fed
On Sat, 16 Sept 2023 at 20:04, Rick Hillegas
wrote:
You are correct. Any vali
Derby INTEGER constants are signed decimal numbers, that is, legal
inputs to the java.lang.Integer.valueOf(String s) method. The radix is
always 10. Hex/octal constants won't work, as you've discovered.
On 9/24/23 9:05 AM, John English wrote:
Is there a way to use hex constants as integers in
You are correct. Any valid user can create as many databases as they
want, provided that the databases are created in a part of the file
system which is write-accessible to the engine jar and to the account
which runs the server. There is no way to prevent a valid user from
creating databases.
Derby builds and tests cleanly with Open JDK build 21+35-2513. See
https://issues.apache.org/jira/browse/DERBY-7155
Regards,
-Rick
On 8/22/23 7:15 AM, David Delabassee wrote:
Greetings!
JDK 21 is now in the Release Candidate Phase so everything is on track for the
Java 21 GA release on
I never use the freeze and unfreeze commands but your understanding of
them sounds correct and is consistent with the following ij experiment:
ij version 10.17
ij> CONNECT 'jdbc:derby:zdb;create=true';
ij> CREATE TABLE t(a INT);
0 rows inserted/updated/deleted
ij> INSERT INTO t VALUES (1);
Thanks, David. Derby builds and tests cleanly with Open JDK build
21-ea+33-2490. See https://issues.apache.org/jira/browse/DERBY-7155
On 7/28/23 2:26 AM, David Delabassee wrote:
Welcome to the OpenJDK Quality Outreach summer update.
JDK 21 is now in Rampdown Phase Two [1], its overall feature
Nothing from me. Thanks, Bryan
On 6/29/23 7:04 AM, Bryan Pendleton wrote:
Hi all, it's time for our quarterly report, please let me
know of any updates about community activities in
April-June that we should include!
Our report isn't due for another 2 weeks, but I'll
be away from keyboard for
On 4/3/23 5:50 AM, Bryan Pendleton wrote:
Hi all, it's time for our quarterly report, please let me
know of any updates about community activities this
winter that we should include!
thanks,
bryan
Thanks, Bryan. Nothing from me.
Thanks for the heads-up, David. Derby builds and tests cleanly with Open
JDK build 20+36-2344.
On 2/14/23 9:32 PM, David Delabassee wrote:
Welcome to the latest OpenJDK Quality Outreach update!
The first Release Candidates of JDK 20 have been released [1] as per
the schedule [2]. At this
I can think of two solutions to your problem:
1) Write a custom Java collator and install it as the default sort order
for all string data in your database. See the following sections in the
Derby Developer's Guide:
https://db.apache.org/derby/docs/10.16/devguide/cdevcollation.html and
Thanks, David. I can confirm that Derby builds and tests cleanly using
Open JDK build 20-ea+32-2328. Cheers
On 1/24/23 9:11 PM, David Delabassee wrote:
Hi,
First off, on behalf of Oracle’s Java Team, I’d like to wish you a
happy and prosperous new year!
In 2023, two Java releases will be
--Original Message-----
From: Rick Hillegas
Sent: 09 January 2023 21:19
To: Kevin Walls ; derby-dev@db.apache.org
Cc: David Delabassee
Subject: Re: FW: Re: [External] : Re: JDK 20 Rampdown Phase 1 & Valhalla LW4
Early-Access builds
Thanks for running that experiment, Kevin. I have reproduced you
Hi Bryan,
Thanks again for taking care of this chore. Nothing comes to mind.
On 1/10/23 4:45 AM, Bryan Pendleton wrote:
Apparently, during the holiday season, I forgot about our reporting
schedule, and our quarterly report to the board is due tomorrow.
Please let me know of any topics we
Thanks for running that experiment, Kevin. I have reproduced your
results, re-enabled the skipped MBean tests, and documented this on
https://issues.apache.org/jira/browse/DERBY-7149.
While I have your attention, what should developers do when they see a
"java.io.InvalidClassException: filter
://bugs.openjdk.org/browse/JDK-8295938
(3)
https://github.com/openjdk/jdk20/commit/628820f47ef9c9ad3cc62e68db9c4dbc7e659154
Thanks,
--David
On 21/12/2022 02:36, Rick Hillegas wrote:
Hi David,
Open JDK build 20-ea+27-2213 introduces another problem. I see the
following error when unmarshalling an object
Happy New Year, Stanimir. I have not looked into this further. I gave up
after sinking a fair amount of time into a seemingly plausible solution.
The MERGE implementation is unfortunately limited and brittle. It is
hard to fix one problem without breaking something else. At this time, I
don't
JVM that is throwing the exception, right ?
Can you try to comment the filter in
`JDK/conf/management/management.properties` ?
--David
On 21/12/2022 19:25, Rick Hillegas wrote:
Thanks for those pointers, David. I'm afraid that my naive attempts
have failed to circumvent this filtering. All of the
Since it only happens with Derby 10.15 onward, the problem is probably
caused by a misconfigured classpath: Derby 10.15 requires more jar
files. I would take this up with the Netbeans community and point them
at the release notes for 10.15.1.3:
4
Thanks,
--David
On 21/12/2022 02:36, Rick Hillegas wrote:
Hi David,
Open JDK build 20-ea+27-2213 introduces another problem. I see the
following error when unmarshalling an object on behalf of an MBean:
java.io.InvalidClassException: filter status: REJECTED
I do not see this problem under b
Hi David,
Open JDK build 20-ea+27-2213 introduces another problem. I see the
following error when unmarshalling an object on behalf of an MBean:
java.io.InvalidClassException: filter status: REJECTED
I do not see this problem under build 19+36-2238.
Can you point me at the experts who can
Thanks for the quick response, Alan. One comment inline...
On 12/15/22 12:24 PM, Alan Bateman wrote:
On 15/12/2022 19:14, Rick Hillegas wrote:
I see many warnings when I build Apache Derby's code and javadoc with
Open JDK build 20-ea+27-2213. In particular, I see a number of
warnings
I see many warnings when I build Apache Derby's code and javadoc with
Open JDK build 20-ea+27-2213. In particular, I see a number of warnings
introduced by the following change:
- JDK-8294241: Deprecate URL public constructors
I naively tried to fix these warnings by changing instances of
Thanks for the heads-up, David. I see many deprecation warnings and
javadoc warnings when I build Derby with Open JDK build 20-ea+27-2213.
Right now, I am trying to track down a fix for the problems introduced
by this change:
- JDK-8294241: Deprecate URL public constructors
My naive attempt
th the url handle of your
Derby code library (file:///Users/me/derbyInstallation/10.15.2.0/) so
that the lines look like this:
grant codeBase"file:///Users/me/derbyInstallation/10.15.2.0/derbyshared.jar"
Hope this helps,
-Rick
Thanks for the help.
On Fri, 25 Nov 2022 at 21:02,
/tadminappschangingyourclasspath.html
and
https://db.apache.org/derby/docs/10.15/publishedapi/org.apache.derby.server/module-summary.html
On 11/25/22 9:51 AM, Rick Hillegas wrote:
This indicates that the server is running with a Java SecurityManager
and that the policy file does not grant read
This indicates that Derby cannot find the localized messages for your
environment. Only the English messages are bundled inside derby.jar.
What happens when you run the following program:
import java.sql.*;
import java.util.*;
public class Z
{
public static void main(String... args)
e no
problems.
Best Regards
-fed
On Thu, 24 Nov 2022 at 19:52, Rick Hillegas wrote:
The SQLState indicates that the server was not able to boot the
database. Look in the server-side derby.log to see if there is a
detailed error message describing why the boot failed.
On 11/23/22 4:42 PM, fed
The SQLState indicates that the server was not able to boot the
database. Look in the server-side derby.log to see if there is a
detailed error message describing why the boot failed.
On 11/23/22 4:42 PM, fed wrote:
Hi,
Sorry for the late answer but I lost your reply.
Two tests:
I have a
On 10/8/22 7:23 AM, Bryan Pendleton wrote:
Hi, it's time to compile our October report to the board.
Please let me know of anything in particular we should include.
thanks,
bryan
Nothing from me. Thanks.
r.txn.AsyncAutoCommitTransaction.enqueue(AsyncAutoCommitTransaction.java:294)
at org.apache.qpid.server.message.RoutingResult.send(RoutingResult.java:124)
On Fri, Sep 30, 2022 at 2:46 PM Rick Hillegas
wrote:
I don't have any theories yet about what is going on. Can you try
issuing the following statement jus
he
code is inside a try-catch-finally that is inside a TimerTask.
conn = newConnection();
LOGGER.info("connection.getAutoCommit() is " + conn.getAutoCommit());
LOGGER.info("Compressing qpid_queue_entries");
conn.prepareStatement("call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP',
I'm not an expert on the table compression code, but it does need an
overhaul (see https://issues.apache.org/jira/browse/DERBY-3683).
If I'm interpreting the error correctly, the table compressor is blocked
trying to escalate its lock on the SYSCONGLOMERATES row from shared to
exclusive. But
Thanks, David. Derby built and tested cleanly with build 36 of Open JDK
19. See https://issues.apache.org/jira/browse/DERBY-7133
On 8/22/22 6:16 AM, David Delabassee wrote:
Greetings!
I hope you had a chance to take some time off. On our side, and
despite the summer vacation, everything is
Thanks for the heads-up, David. Derby builds and tests cleanly with JDK
19 build 19-ea+32-2220. See the last comment on
https://issues.apache.org/jira/browse/DERBY-7133.
On 7/25/22 7:56 AM, David Delabassee wrote:
Greetings!
JDK 19 is now in Rampdown Phase Two [1]. The overall feature set is
On 7/7/22 2:03 AM, John English wrote:
On 05/07/2022 17:26, Rick Hillegas wrote:
In any event, as you've noticed, getLabelName() returns the same
value as getColumnName() in Derby.
So basically I need to write my own SQL parser for a sequence of
SelectItems between SELeCT and FROM if I want
On 7/5/22 5:46 PM, Bryan Pendleton wrote:
Hi Derby-dev, I'm preparing our quarterly report to the Board.
For this quarter, I think the main item of interest for the
Derby sub-project is the 10.16.1.1 release.
Is there anything else we should include in our report?
thanks,
bryan
Can't think
On 7/4/22 11:50 AM, John English wrote:
On 04/07/2022 16:21, Rick Hillegas wrote:
I'm afraid I don't understand your results. When I run your
experiment, "2" is the name and label of the second column of the
query "SELECT country,count(*) FROM customer GROUP BY country ORDER
BY
I'm afraid I don't understand your results. When I run your experiment,
"2" is the name and label of the second column of the query "SELECT
country,count(*) FROM customer GROUP BY country ORDER BY country". Does
the following give you what you want:
SELECT country,count(*) AS "count(*)"
Thanks, David. We have adjusted Derby so that it builds cleanly without
the new deprecation warnings introduced by Open JDK build 19-ea+27-2074.
For more details, see the discussion on
https://issues.apache.org/jira/browse/DERBY-7133.
On 6/13/22 6:18 AM, David Delabassee wrote:
Greetings!
The Apache Derby project is pleased to announce feature release 10.16.1.1.
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
The Apache Derby project is pleased to announce feature release 10.16.1.1.
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
The Apache Derby project is pleased to announce feature release 10.16.1.1.
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
Thanks for that suggestion, Bryan. Here is a second draft:
--
The Apache Derby project is pleased to announce feature release 10.16.1.1.
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
Here is a first draft. Please let me know how to improve it.
---
The Apache Derby project is pleased to announce feature release 10.16.1.1.
Apache Derby is a sub-project of the Apache DB project. Derby is a pure
Java relational database engine which conforms to
there were no errors to correct, I issued that command. The
upload continued without further errors. I verified that the artifacts
were all uploaded to the Nexus staging repository.
Thanks to everyone who helped me puzzle through this,
-Rick
On 6/14/22 6:51 AM, Rick Hillegas wrote:
Thanks for looking
, no proxy or whatever in
between your maven process and repo.a.o?
HTH
T
On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas
wrote:
Thanks, Tamas. On your advice, I updated the top level pom to refer to
version 26 of the parent apache pom. This caused the maven-antrun-plugin
to object that a maj
ever in
between your maven process and repo.a.o?
HTH
T
On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas
wrote:
Thanks, Tamas. On your advice, I updated the top level pom to refer to
version 26 of the parent apache pom. This caused the maven-antrun-plugin
to object that a major upgrade had obsol
maybe some misbehaving proxy in between maven process and
repo.apache.org?
HTH
Tamas
On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas
wrote:
I need advice about how to move past a "peer not authenticated" error.
I am trying to stage some 20 jars and corresponding poms via the
followi
I need advice about how to move past a "peer not authenticated" error.
I am trying to stage some 20 jars and corresponding poms via the
following command:
mvn -Dgpg.passphrase="my secret passphrase" clean deploy
I am able to upload most of the artifacts, but the command eventually
fails
ither.
My instinct is that your maven settings file is somehow incorrect, and
maven isn't helping you figure out what's wrong with it :(
bryan
On Wed, Jun 8, 2022 at 9:17 AM Rick Hillegas wrote:
I am stuck at the step for using maven to publish 10.16.1.1 artifacts.
The details of the issue ca
19:26, Karl Heinz Marbaise wrote:
Hi Rick,
On 10.06.22 17:55, Rick Hillegas wrote:
I am having trouble signing maven artifacts. The details of the problem
are described at https://issues.apache.org/jira/browse/INFRA-23348. The
maven error message is terse. No additional useful information comes
I am having trouble signing maven artifacts. The details of the problem
are described at https://issues.apache.org/jira/browse/INFRA-23348. The
maven error message is terse. No additional useful information comes
back when I run the maven command with -e and -X switches. I haven't
found any
xml?
from mobile (sorry for typos ;)
On Thu, Jun 9, 2022, 06:22 Rick Hillegas wrote:
I am having trouble signing maven artifacts for a new Derby release
(10.16.1.1). The details of the problem are described at
https://issues.apache.org/jira/browse/INFRA-23348. The release itself is
publis
I am having trouble signing maven artifacts for a new Derby release
(10.16.1.1). The details of the problem are described at
https://issues.apache.org/jira/browse/INFRA-23348. The release itself is
published on the Apache mirrors and can be downloaded from
I am stuck at the step for using maven to publish 10.16.1.1 artifacts.
The details of the issue can be found at
https://issues.apache.org/jira/browse/INFRA-23348
In a nutshell, I have uploaded artifacts and checksums but not gpg
signatures. I do not know how to generate/upload these
The publication of 10.16.1.1 cannot start until the cwiki is available.
That's where our release publication instructions live. The cwiki is
undergoing some kind of maintenance right now.
FYI
Forwarded Message
Subject:[RESULT] [VOTE] 10.16.1.1 Release
Date: Fri, 3 Jun 2022 09:06:49 -0700
From: Rick Hillegas
To: derby-...@db.apache.org
Thanks for catching that, Bryan. Re-sending...
On 6/2/22 5:43 PM, Bryan Pendleton wrote:
Not a huge deal
Thanks for catching that, Bryan. Re-sending...
On 6/2/22 5:43 PM, Bryan Pendleton wrote:
Not a huge deal, Rick, but the subject line of your message is wrong! :)
bryan
On Thu, Jun 2, 2022 at 5:28 PM Rick Hillegas wrote:
Thanks for everyone's work on coding, documenting, and testing
FYI
Forwarded Message
Subject:[RESULT] [VOTE] 10.15.2.0 Release
Date: Thu, 2 Jun 2022 17:28:46 -0700
From: Rick Hillegas
To: derby-...@db.apache.org
Thanks for everyone's work on coding, documenting, and testing
10.16.1.1. The polls have closed
Thanks for everyone's work on coding, documenting, and testing
10.16.1.1. The polls have closed. The community has approved 10.16.1.1
as an official Derby release:
+1:
Dag Wanvik (pmc)
Bryan Pendleton (pmc)
Rick Hillegas (pmc)
No other votes were cast.
1 - 100 of 12861 matches
Mail list logo
