Hi,
I improved the TCK-test for Optional.
With the latest datanucleus (5.0.0-release-SNAPSHOT) there is are some
problems remaining:
1) "SELECT FROM org.apache.jdo.tck.pc.query.OptionalSample WHERE
!(optionalPC.optionalPC.isPresent())"
I think this should only return an object A if A
Dear all,
I'm trying to implement the schema for the new Optional test, but I keep
running into a ClassCastException:
javax.jdo.JDOFatalInternalException: Failed to generate new Mapping of
type org.datanucleus.store.rdbms.mapping.java.OptionalMapping, exception
: Failed to generate new
to update the implementation.
Cheers,
Tilmann
On 30-May-16 21:31, Craig Russell wrote:
Hi Tilmann,
On May 30, 2016, at 6:10 AM, Tilmann Zäschke <zaesc...@gmx.de> wrote:
Dear all,
I'm trying to implement the schema for the new Optional test, but I keep
running into a ClassCastExc
Hi,
More likely the problem is down to having a field as Optional
The test doesn't actually have Optional, but it does have:
Optional optionalAny;
Optional optionalNoGenerics;
I suppose these would not be allowed either (because they are mostly
equivalent to Optional)?
Regards,
Tilmann
Hello Hei,
sorry, I posted my answer first only to the dev list, I'm not sure you
are on it.
So here it is again, with some updates:
Hi,
I haven't read the whole post in detail, but I understand the main idea
is garbage collection in databases. This reminds me of similar concepts
in osome
Hi,
I believe the 'j...@apache.org' list is missing from lists.apache.org .
Could you please add it? I think it is meant to be public.
Cheers,
Tilmann (tilma...@apache.org)
Hi Andy,
(sorry for double posting, I sent this to an...@apache.org before)
I started looking into adapting datanucleus for JDO JIRA 747:
https://issues.apache.org/jira/browse/JDO-747
Some time ago you offered to give some initial pointers, could you tell
me where to start?
My first goal:
Hi,
a quick recap of the discussion we had in the last telecon. This was
sparked by the discussion whether Query.compile() may need database
access, i.e. whether it should fail when called outside transaction
borders.
(TL;DR): See conclusion below.
Querying usually requires the following
Nov 13, 2017, at 12:28 PM, Tilmann Zäschke <tilmann_...@gmx.de> wrote:
Hi,
is anyone else having trouble accessing the JDO SVN repo?
Neither SVN checkout on console nor the web-view (https://svn.apache.org/viewvc/db/jdo)
appears to work, they just hang: "The server at svn.apache.org i
Hi,
is anyone else having trouble accessing the JDO SVN repo?
Neither SVN checkout on console nor the web-view
(https://svn.apache.org/viewvc/db/jdo) appears to work, they just hang:
"The server at svn.apache.org is taking too long to respond."
I first tried yesterday, but it is still not
Hi,
After the last telecon (that I attended) I had a look at various DBMS
for their handing of SEQUENCEs and schema
spaces.
If I remember correctly, the question in the telecon was to see which
DBMS support schema names for sequences.
I am a bit unclear now how this relates to the ticket,
Dear all,
please have a look here:
https://docs.google.com/presentation/d/19RoED9sc2oAA1TrbENYNUwNPSnOU3P6Cd3DwvD4HqDY/edit?usp=sharing
I hope this is useful for drafting a new website layout.
Cheers,
Til
Hi Michael,
so the following worked mostly:
org.junit.vintage
junit-vintage-engine
5.7.0
but if properly failed in the end with:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-clean-plugin:3.1.0:clean (default-clean)
on project jdo: Failed to clean project: Failed to
change near the top.
Cheers,
Til
On 05/11/2020 20:33, Craig Russell wrote:
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday November 12 10:30 AM PST
Agenda:
1. JDO-785 "Update release instructions for new website and release process"
https://issues.
yes it does, we merged 4 (or 5?) PRs today, but I agree it is a bit noisy.
@Michael, should we put this on the agenda for next time?
tilmann
On 04/02/2021 21:29, Bryan Pendleton wrote:
Seems like the new website machinery generates a lot of messages?
bryan
-- Forwarded message
t; in Nexus to check for sha256/512 instead of sha1/md5
--
Key: INFRA-22540
URL: https://issues.apache.org/jira/browse/INFRA-22540
Project: Infrastructure
Issue Type: Improvement
Components: Nexus
Reporter: Tilmann Zäschke
Priority
Hi Craig,
apparently we missed each other by a few minutes only, we stuck around
until 20:07...
We discussed the INFRA issue.
One alternative would be to wait a few days, and if it doesn't look like
its going to be solved in the next week, we could just release RC4
anyway (RC3 is burnt), with
Dear all,
I just staged JDO 3.2 RC2. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1002
Changes:
- archives are now available as .zip and as .tar.gz
- the "source-release" archives are now signed with SHA512
- The pom now has the
Dear all,
we have a new release candidate so this vote on RC4 is cancelled.
I will send out another email with a new vote for RC5.
Kind regards,
Til
On 25/11/2021 22:52, Tilmann wrote:
Hi,
Please vote on the JDO 3.2 release. Voting will be open until Monday,
November 29.
You may download
Dear all,
I prepared the final release for JDO 3.2.
Please vote on the release. Voting will be open until Monday, January 31st.
You may download the JDO 3.2 release artifacts from the staging repository:
https://repository.apache.org/content/repositories/orgapachejdo-1006/
The JDO API
Hi,
Updating the DB website succeeded, but the subproject websites
disappeared. I reported this here:
https://issues.apache.org/jira/browse/INFRA-22822
https://db.apache.org/
Any help is appreciated.
Best,
Til
The Apache JDO project is pleased to announce a new release 3.2.
Java Data Objects (JDO) is a standard way to access persistent data in
databases, using plain old Java objects (POJO) to represent persistent data.
JDO 3.2 can be obtained from the JDO download site:
Hi,
thanks for the update. Should we add some explanations what the columns
mean (DFG, PK, Persistent)?
Best,
Til
On 4/11/22 17:33, github-...@apache.org wrote:
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch publish
in repository
Dear all,
JDO 3.2.1 (based on 3.2.1 RC2) has been approved as an official Apache
JDO release. Thanks to
all who worked on the release and who voted.
+1
Craig Russell (pmc)
Michael Bouschen (pmc)
Tilmann Zäschke (pmc)
Tobias Bouschen (Committer)
There were no other votes.
Kind regards,
Til
[ERROR]
Any ideas? I get the same thing with the main branch, so it's probably
something in my local envt.
Thanks,
Craig
On May 22, 2022, at 07:28, Tilmann Zäschke wrote:
Hi,
please vote on the JDO 3.2.1 release (based on RC2). Voting will be open until
Wednesday,
May 25th, 14:30 UTC.
Y
The Apache JDO project is pleased to announce a new release 3.2.1.
Java Data Objects (JDO) is a standard way to access persistent data in
databases, using plain old Java objects (POJO) to represent persistent
data.
JDO 3.2.1 can be obtained from the JDO download site:
Dear all,
I just staged JDO 3.2.1 RC1. Please have a look and report any problems:
https://repository.apache.org/content/repositories/orgapachejdo-1007/
Kind regards,
Tilmann
Hi,
please vote on the JDO 3.2.1 release (based on RC2). Voting will be open
until Wednesday,
May 25th, 14:30 UTC.
You may download the JDO 3.2.1 release artifacts from the staging
repository:
https://repository.apache.org/content/repositories/orgapachejdo-1008/
The JDO API release
+1
Regards,
Tilmann
On 22/05/2022 16:28, Tilmann Zäschke wrote:
Hi,
please vote on the JDO 3.2.1 release (based on RC2). Voting will be
open until Wednesday,
May 25th, 14:30 UTC.
You may download the JDO 3.2.1 release artifacts from the staging
repository:
https://repository.apache.org
Hi,
has anyone else trouble joining the telecon?
Til
On 13/07/2022 20:39, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday July 14 11:00 AM Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to
discuss JDO TCK issues and status.
We use the following
@Michael Can you maybe leave and start it again? It just says "call
ended" on my side (from last week)
Til
On 14/07/2022 20:11, Bouschen, Michael wrote:
Hi,
no, I joinded the telecon and I'm still in.
Regards Michael
Hi,
has anyone else trouble joining the telecon?
Til
On 13/07/2022
When I try to start it it just does nothing.
On 14/07/2022 20:08, Craig Russell wrote:
I have not seen it start yet...
On Jul 14, 2022, at 11:07, Tilmann Zäschke wrote:
Hi,
has anyone else trouble joining the telecon?
Til
On 13/07/2022 20:39, Michael Bouschen wrote:
Hi,
We will have
Dear all,
unfortunately I cannot attend tomorrow. See you all next week.
Best,
Til
On 25/08/2022 21:06, Craig Russell wrote:
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday September 1 1100 PDT 2000 CEDT
Agenda:
1. JIRA JDO-817 "
Dear all,
my apologies, but again something came up and I cannot make it tomorrow.
Regards,
Tilmann
On 14/09/2022 21:04, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday September 15 11:00 Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to
Wednesday October 12 at noon PDT 21 CEDT
Works for me.
Best, Til
On 11/10/2022 18:47, Bouschen, Michael wrote:
Hi Craig,
we could have the meeting Wednesday October 12 at noon PDT 21 CEDT, in case
that helps.
What do the others think?
Regards Michael
Hi,
Sorry for the late notice,
Has the meeting already started? I can't get in ("The meeting host
will let you in soon")
On 04/01/2023 22:21, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday January 5 11:00 Pacific
Standard Time (PST) 20:00 Central European Time (CET) to discuss JDO
TCK
Michael,
just to let you know, I got the Attribute test case working. I'll let
you know if I hit any more issues. I will clean up and commit soon
(hopefully).
I hope you haven't invested too much time yet...
Best,
Til
I submitted an issue here:
https://github.com/datanucleus/datanucleus-api-jdo/issues/127
Best,
Til
On 29/01/2023 12:48, Tilmann Zäschke wrote:
Michael,
just to let you know, I got the Attribute test case working. I'll let
you know if I hit any more issues. I will clean up and commit soon
Unfortunately I have to skip tomorrow, something came up.
Best,
Til
On 01/02/2023 21:06, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday February 2 11:00 Pacific
Standard Time (PST) 20:00 Central European Time (CET) to discuss JDO
TCK issues and status.
We use the
Sorry, just got the blue screen of death.
Next week Thursday is fine if you haven't decided yet...
Cheers, Til
On 15/03/2023 21:02, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday March 16 12:00 Pacific
Daylight Time (PDT) 20:00 Central European Time (CET) to discuss
I am getting "the host has another meeting in progress" ...?
On 01/03/2023 18:57, Tobias Bouschen wrote:
Hi all,
sorry for the short notice again, but I won't be able to attend
today's conference call. I will see you all next week.
Best regards,
Tobias
On 28/02/2023 20:58, Michael
I had the same problem (1.8.0-331 is not in the allowed range [11,).)
My simple workaround was to use Java 11 (or later) to run the tool.
You can also try autoformatting from your IDE, just check that it
formats only what you want to be changed.
But I agree that we should probably discuss
Hi Michael,
in the minutes last week it said:
Next meeting: Thursday February 9 1200 PST 2100 CET
Is it Feb 8 or Feb 9?
If it is today, I cannot make it, I will simply join next week :-)
Til
On 08.02.23 08:41, Michael Bouschen wrote:
Hi,
We will have our regular meeting Wednesday
These are from four/five distinct events with 1-2 emails each: two
commits, sonarcloud pass, the merge, and finally deleting the branch.
(actually _four_ events, sonarcloud is trigger by commit I think)
One solution may be to have only the PR description in the header so
that all emails
2100 CET works for me.
Best,
Til
On 27/06/2023 18:11, Craig Russell wrote:
I may have a conflict on Thursday June 29 at 1100/2000.
Can we reschedule the call for one hour later? Thursday June 29 1200 PDT 2100
CET.
Thanks,
Craig
Craig L Russell
c...@apache.org
https://community.apache.org/contributors/mailing-lists
That looks good to me. Since these are just .asf.yam setting, I suppose it
should be easy to just try it out?
Best,
Til
On 18/05/2023 02:37, Craig Russell wrote:
Take a look at this:
Great, that works perfectly! :-)
On 21/11/2023 22:22, Michael Bouschen wrote:
Hi,
...
3. JDO-830: "tck: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-830
PR #85 https://github.com/apache/db-jdo/pull/85
Still some issues with ConsoleLauncher writing to log
47 matches
Mail list logo
