-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add ability to manage start modules by java feature #5492
Labels
Comments
joakime
added a commit
that referenced
this issue
Oct 22, 2020
+ Simplifying alpn start modules in the process. (from 11 to 3) Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Feb 15, 2021
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Feb 15, 2021
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Feb 18, 2021
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
joakime
added a commit
that referenced
this issue
Feb 18, 2021
…start-properties Issue #5492 - Adding java.features.* start properties
This was referenced Mar 10, 2021
Closed
This was referenced Mar 10, 2021
This issue has been automatically marked as stale because it has been a |
github-actions
bot
added
the
Stale
For auto-closed stale issues and pull requests
label
Dec 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version
9.4.x
Description
When writing optional modules that depend on Java features (like alpn or loom) you currently have to rely on the
${java.version.platform}
start property.Which means you wind up having multiple *.mod files, one for each major version of java, just to enable/disable modules based on a feature in java.
Proposal is to add new "features" properties to start.jar
aka:
That way we can simplify the maintenance of optional modules.
The text was updated successfully, but these errors were encountered: