Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Java 9 modules specific JVM arguments #119

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Support Java 9 modules specific JVM arguments #119

wants to merge 3 commits into from

Conversation

benoitdesire
Copy link

--add-modules, --add-reads, --add-exports and --add-opens can be
followed by a space and the module/package it applies to. This pair is
split when parsing arguments and should be recombined together.

  • Add a new method addJava9ModulesJvmArg with a state variable
    firstPartJava9ModulesArg to keep the first part of the Java 9 module
    argument, and so remove static qualifier of addJvmArg.

--add-modules, --add-reads, --add-exports and --add-opens can be
followed by a space and the module/package it applies to. This pair is
split when parsing arguments and should be recombined together.
- Add a new method addJava9ModulesJvmArg with a state variable
firstPartJava9ModulesArg to keep the first part of the Java 9 module
argument, and so remove static qualifier of addJvmArg.
@muryoh
Copy link

muryoh commented Jul 5, 2018

Hey, any chance in this getting merged or reviewed? :-)

Cheers

@benoitdesire
Copy link
Author

Hi @pron

We would need this soon for a release.
Would it be possible to have a look please ?

Best regards

Benoit Desire and others added 2 commits November 15, 2018 17:37
It is called when reolving native dependencies line 2512 and
when resolving boot classpath line 2281. And it happens that these
functionalities are not used, it is the case in our product, and it
still works perfectly. Nothing to be warned of...

Change-Id: I247f59b214749e0211090f254e0a3ea5cb069389
Checking the last extraction time is after the jar file time isn't
enough for development version.
We have issues where we first build multiple dev versions and then
test/deploy them a day after. In this case, the cache won't be cleaned
up and the app classpath may be wrong.
Now if you change the jar, it re-extracts.

Change-Id: I9648e2ef7b7fa031b8455465c6bc605fc1c71e72
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants