Allow ${project.basedir} in profile activation.condition - #11528
Merged
gnodet merged 1 commit intoDec 9, 2025
Merged
Conversation
Previously, ${project.basedir} was only allowed in activation.file.exists
and activation.file.missing. This change extends the same allowance to
activation.condition, which is a new Maven 4.0.0 feature that also needs
to reference the project base directory for its expressions.
This fixes a false positive warning when using expressions like
exists("${project.basedir}/src/main/java") in activation conditions.
cstamas
approved these changes
Dec 9, 2025
gnodet
added a commit
to gnodet/maven
that referenced
this pull request
Dec 9, 2025
Previously, ${project.basedir} was only allowed in activation.file.exists
and activation.file.missing. This change extends the same allowance to
activation.condition, which is a new Maven 4.0.0 feature that also needs
to reference the project base directory for its expressions.
This fixes a false positive warning when using expressions like
exists("${project.basedir}/src/main/java") in activation conditions.
(cherry picked from commit fde7213)
Contributor
Author
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
gnodet
added a commit
that referenced
this pull request
Dec 9, 2025
…1531) Previously, ${project.basedir} was only allowed in activation.file.exists and activation.file.missing. This change extends the same allowance to activation.condition, which is a new Maven 4.0.0 feature that also needs to reference the project base directory for its expressions. This fixes a false positive warning when using expressions like exists("${project.basedir}/src/main/java") in activation conditions. (cherry picked from commit fde7213)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously,
${project.basedir}was only allowed inactivation.file.existsandactivation.file.missing. This change extends the same allowance toactivation.condition, which is a new Maven 4.0.0 feature that also needs to reference the project base directory for its expressions.This fixes a false positive warning when using expressions like
exists("${project.basedir}/src/main/java")in activation conditions.Changes
DefaultModelValidatorto allow${project.basedir}inactivation.conditionpathPull Request opened by Augment Code with guidance from the PR author