Update Payara Micro Dev Mode Property Names Based on Plugin Version #8899
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This PR updates the configuration logic to align with the version-specific property naming conventions introduced in the Payara Micro Maven Plugin.
Depending on the plugin version, system properties used to enable Dev Mode features will now automatically match the expected format.
Details:
🔹 For plugin version ≥ 2.5
Payara Micro Maven Plugin 2.5 introduced a new convention where system properties are prefixed with
payara.
.Example command:
Code changes ensure that when the detected plugin version is 2.5 or later, the configuration uses these new prefixed property names (e.g.
payara.hot.deploy
,payara.deploy.war
, etc.).🔹 For plugin version ≥ 2.1 and < 2.5
Earlier versions (starting from 2.1) introduced Dev Mode but used unprefixed property names.
Example command:
The logic now sets these unprefixed keys automatically for compatibility with 2.1–2.4.
🔹 For plugin version < 2.1
Dev Mode was not supported in versions earlier than 2.1, so Dev Mode-related properties are skipped.
Legacy properties like
payaraVersion
andhotDeploy
are still set if provided to maintain basic compatibility, but Dev Mode-specific flags are ignored.Motivation:
Ensures that NetBeans-generated Payara Micro Dev Mode configurations work seamlessly across all supported plugin versions, eliminating property mismatches and startup failures due to version differences.
Testing:
payara-micro-maven-plugin
versions 2.0, 2.1, and 2.5