You are right, I forgot that that still exists. :-S I do think that that
way of dependency management is highly discouraged and IMNSHO should be
discarded in your build as a first step.
With regards,
Nick Stolwijk
~~~ Try to leave this world a little better than you found it and, when
your turn
Le mar. 22 mars 2022 à 23:37, Nick Stolwijk a
écrit :
> Also, org.codehaus.groovy:groovy-eclipse-batch:RELEASE is not in
> Maven Central.
Yes it is:
https://search.maven.org/artifact/org.codehaus.groovy/groovy-eclipse-batch
About the RELEASE version:
As far as I can see is the support for Java 8 not yet dropped from Groovy
Eclipse. Also, org.codehaus.groovy:groovy-eclipse-batch:RELEASE is not in
Maven Central. Could it be that someone built it locally and uploaded that
artifact to your repository? Maybe you can better rely on the artifacts
And I also determined that groovy-eclipse v4.0.1 was released on 3/6/22, so it
just took a few days to get to our intranet repo. I don't see any statement
about it being built with Java 11, but it appears that's what happened.
> -Original Message-
> From: KARR, DAVID
> Sent: Tuesday,
Here is the maven-compiler-plugin block:
maven-compiler-plugin
${maven.compiler.plugin.version}
Correction, it wasn't the "ecj" artifact, that was compiled with Java 11, it
was "groovy-eclipse-batch". I still have to understand how this could happen,
and what are reasonable mitigations we can set up to prevent this.
I found these artifacts in our intranet maven repo. The "4.x" artifacts
This is totally unexpected behavior to me: an external artifact whose
content would be different depending on which JDK downloaded it.
Would you mind sharing the maven-compiler-plugin declaration with the ecj
dependency? (to try replicating the issue and understand it)
Le mar. 22 mars 2022 à
Self-replying from my alter ego.
I have verified that if I remove the "ecj" tree from my local repo, then build
one service with Java 11, with just "mvn package", then run a build of a
different service with Java 8, it will get the given error. I can verify that
the ecj artifact is now
Our org's builds have been using Java 8 for quite a while. We're starting
to move some builds to Java 11. We're seeing some builds failing with the
following:
-
Execution default-compile of goal
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile failed:
An API
