Hi,
We will have our regular meeting Thursday June 23 11:00 AM Pacific
Daylight Time (PDT) 21:00 Central European Summer Time (CEST) to discuss
JDO TCK issues and status.
We use the following dial-in for audio and video. You need a Skype
account to join.
https://join.skype.com/lKWOxZDu2O5U
Here's an update on item 2.
I installed a new MacOSX Monterey 12.4 and a new Java from Oracle and removed
JAVA_HOME from my .cshrc. So my environment is completely different from the
last time I built JDO.
When I try mvn clean install:
[MacBook-Pro-10:~/apache/git/db-jdo] clr% mvn clean instal
Hi Craig,
please try setting JAVA_HOME to the JDK you want to use. As far as I know uses
maven the JAVA_HOME environment variable internally to find the JDK. This might
explain the error message you get: "No compiler is provided in this
environment. Perhaps you are running on a JRE rather than
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting in two weeks: Thursday July 7 1100 PDT 2000 CEDT
Agenda:
1. Branches 3.2 and 3.2.1: anything left?
The plan is to keep these branches as they are in case any follow-on releases
are needed, e.g. 3.2.2 or 3.2.1.1 and the ma
Hi,
Still looking for help on this one. I added a JAVA_HOME env variable.
Exactly the same result:
[MacBook-Pro-10:~/apache/git/db-jdo] clr% mvn clean install
Maven config from .mavenrc
[INFO] Scanning for projects...
[INFO] --
Hi Craig,
the first output of your mvn clean install call says "Maven config from
.mavenrc".
Does it include any java setting? How does it look like? I do not have
such a config file .mavenrc.
Regards Michael
Hi,
Still looking for help on this one. I added a JAVA_HOME env variable.
Exa
Hi Michael,
Thanks for checking... You found the issue.
My .mavenrc:
clr% cat ~/.mavenrc
echo "Maven config from .mavenrc"
export JAVA_HOME=$(/usr/libexec/java_home -v 1.8)
So that needs to be changed (or removed since it has no value).
I also looked at the difference between the api module whi
Hi Craig,
about the test failure in the api submodule:
I'm wondering whether it has to do with the changes for JDO-815 "Change
headers on source files to use https:// instead of http:".
I propose you stash your changes (or clone the db-jdo repository into a
new directory) and do a mvn clean i
Hi Michael,
Since I had not really changed anything except my environment, I started with a
clean main branch. The only thing I've changed is the pom to make the compiler
work (and removed the errant .mavenrc).
clr% echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_71.jdk/Contents/Home
Hi Craig,
I think your JDK version is too old. I downloaded jdk-8u71, installed it and
see the same errors.
When I use jdk-8u201 everything compiles and runs fine.
Any reason why you are using such an old Java 8 version?
I switched to openjdk from adoptOpenJDK or from Azul (Zulu).
Regards Micha
I had installed the new java 8 version u333 but it looks like I just installed
a jre.
So now I have a proper jdk 8u331. And the most recent maven 3.8.6.
clr% java -version
java version "1.8.0_331"
Java(TM) SE Runtime Environment (build 1.8.0_331-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25
Hi Craig,
what do I need to do to see these warnings?
I do not get the warnings, neither with Java 8 (OpenJDK Runtime
Environment (Zulu 8.42.0.23-CA-macosx) (build 1.8.0_232-b18)) nor with
Java 11 (OpenJDK Runtime Environment Zulu11.52+13-CA (build 11.0.13+8-LTS)).
I agree we should fix thes
Hi Michael,
When I was debugging my compile issue I added this to the pom.xml in the tck
module:
org.apache.maven.plugins
maven-compiler-plugin
true
true
-Xlint:unchecked
I created a new branch tck-compiler-warnings to track this. There will be many
changes to eliminate all warnings...
Craig
> On Jun 27, 2022, at 15:51, Craig Russell wrote:
>
> Hi Michael,
>
> When I was debugging my compile issue I added this to the pom.xml in the tck
> module:
>
14 matches
Mail list logo
