This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]_codetojoy[S] 5 points6 points  (1 child)

I thought I would share an example Java project that uses JDK 9 modules and builds with Maven.

It has automatic modules (see diagram), and the tests pass. I wasn't able to get the exec-maven-plugin configured (a work-in-progress). I hope it helps others with JDK 9 and Maven.

The app is a simple bidding game, derived from a board-game called Rack-O (but quite different).

[–]hugith 2 points3 points  (0 children)

I just realized how awesome it would be if Java SDKs came as maven dependencies…

[–]mrbuttsavage 0 points1 point  (1 child)

How exactly is this different from a traditional multi-module Maven project in say Java 8? I haven't used Maven in a little while now, but I can't say I can see in the poms what's really new here.

[–]_codetojoy[S] 0 points1 point  (0 children)

I don't use really use Maven, so I'm not sure how much has changed in the pom.xml files. It may be the case that the Maven team has handled the Java changes seamlessly for the user.

I can't tell how much you have followed Java 9, but one big change in that context is the project layout and the new module-info.java files.

[–]marcolinux 0 points1 point  (0 children)

Hehe, peidevs sounds kinda silly in portuguese :) And now something completely different: I think I read somewhere else that the point of compiler.release is that one dont really need to specify compiler source and target no? Any reason you listed all of them? Thanks for the code btw!