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

EXTRA_JVM_ARGUMENTS not working as expected #69

Open
ccarv opened this issue Apr 3, 2019 · 0 comments
Open

EXTRA_JVM_ARGUMENTS not working as expected #69

ccarv opened this issue Apr 3, 2019 · 0 comments

Comments

@ccarv
Copy link

ccarv commented Apr 3, 2019

I am using 2.0.0 of this plugin but have only found documentation for 1.10. I stumbled on a related issue but it doesn't address an alternative solution.

We have a very large multi-module Maven project with several appassembler components. The build POM defines the plugin and a base configuration that is applicable to all of the components within this project, and any component specific changes can be made with some POM properties (main class, additional command line arguments, etc...) at the component level. Everything has worked out great up until the JVM arguments.

I tried using the <extraJvmArguments> option and using a POM property but it doesn't do anything. Per the documentation in 1.10, this should initialize a EXTRA_JVM_ARGUMENTS.

Ideally, it would be nice if each component could have a "options" file where the JVM arguments are defined, and all appassembler would have to do is parse this and translate to the appropriate platform.

Is there any functionality that I could leverage that might give me this option?

Thank you

@ccarv ccarv changed the title EXTRA_JVM_ARGUMENTS not working as expected? EXTRA_JVM_ARGUMENTS not working as expected Apr 3, 2019
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

No branches or pull requests

1 participant