module-info.java 2.11.0 gives error on requires com.google.gson; #2721
-
I tried to upgrade Gson from 2.10.1 to 2.11.0. My module-info.java now gives an error on "requies com.google.gson;" in the eclipse 2024-03 editor for module-info.java. maven 3.9.8 runs OK. eclipse: 2024-03 pom.xml:
module-info.java:
} org.test.Test.java: public class Test Note that gson 20.10.1 has a module-info.class in the root directory of the jar. In gson 20.11.1 it has been moved to META-INF/versions/9 |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
make that 2.10.1 and 1.11.0 |
Beta Was this translation helpful? Give feedback.
-
Gson 2.10.1 had the We had a report about a similar issue before: #2679 |
Beta Was this translation helpful? Give feedback.
-
The problem occurred with spring-boot 3.4.0-M1 introducing Gson 2.11.0 onto an eclipse that doesn't handle multi-release jars (see eclipse-jdt/eclipse.jdt.core#2495). Also, in my 2.10.1 jar there is no module-info.class anywhere in META-INF only in the root of the jar. Anyway, I think this can be closed as a problem with eclipse. |
Beta Was this translation helpful? Give feedback.
-
That is fine! Thanks!
…On Mon, Jul 29, 2024 at 5:41 PM Marcono1234 ***@***.***> wrote:
Anyway, I think this can be closed as a problem with eclipse.
Ok, I have marked my comment above as answer. I hope that is ok for you.
—
Reply to this email directly, view it on GitHub
<#2721 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABY2VUG5W4EQOYXQX3PUGRTZO2ZJJAVCNFSM6AAAAABLSE7E5KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJYGQYTQMA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Gson 2.10.1 had the
module-info.class
underMETA-INF/versions/9
as well.We had a report about a similar issue before: #2679
As mentioned there maybe the Gson JAR changed in some way when we updated Maven plugins or made the build reproducible, however the JAR should still be valid. It seems this might be an issue with Eclipse (see eclipse-jdt/eclipse.jdt.core#2495) since as you mention this only affects Eclipse but does not occur when running Maven from the command line.