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
WildFly Bootable JAR - Add native support for slim Bootable JAR #385
Milestone
Comments
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 23, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 23, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 23, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 23, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 23, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 23, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
jfdenise
added a commit
to jfdenise/jkube
that referenced
this issue
Sep 28, 2020
…pport for slim Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
manusa
pushed a commit
that referenced
this issue
Sep 29, 2020
…m Bootable JAR Signed-off-by: JF Denise <jdenise@redhat.com>
Implemented in #398 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Thanks to JKube workflow, we have the opportunity to benefit from slim Bootable JAR (a Bootable JAR that doesn't contain JBoss modules artifacts) feature. slim Bootable JAR starts fast, this wil lreduce the server startup time.
The WildFlyJar Generator can detect the path to the generated maven repo cache configured in the wildfly-jar-maven-plugin and installs it in the Docker image in /deployments/[directory name].
In addition, the generator adds the -Dmaven.local.repo=/deployments/[directory name] in the JAVA_OPTIONS. That is required for the server to retrieve JBoss modules artifacts. NB: In order for this part to work properly we need a fix for #384
Info
The text was updated successfully, but these errors were encountered: