I see that the changes from SLING-9503 changed the variable replacement in slingfeature-maven-plugin to be more limited.
Is there an expectation that the substitutions for the limited "replacePropertyVariables" values would only use the property value hardcoded in the pom and ignore the system property with the same name? I was expecting that when supplying a system property (with the same name) on the mvn command line, that the value from the system property would be used for the substitutions but is not used and the value always comes from the property defined in the pom. If this is not done on purpose, I can provide a fix to check for a system property value first before a fallback to the project property. Let me know what you think. -Eric