slachiewicz commented on issue #13347: URL: https://github.com/apache/maven/issues/13347#issuecomment-6089333257
Both effects come from hardening I added in #12948 (3.10.x: #12953), with profile activation later moved into a sandboxed activation context by #13112/#13114: a model resolved from a repository interpolates only a fixed set of expressions and does not activate profiles from user properties. Both checks use `validationLevel < VALIDATION_LEVEL_MAVEN_2_0` to decide that a model came from a repository, because `DefaultArtifactDescriptorReader` builds those at `VALIDATION_LEVEL_MINIMAL`. NetBeans builds the user's own project at MINIMAL for leniency, so it is treated as a repository POM: `-D` profile activation stops working, and `maven.model.dependencyInterpolation.full` cannot bring it back. The validation level is the wrong signal for this. I'll open a PR for master and 3.10.x that adds an explicit flag on the model building request, set by `DefaultArtifactDescriptorReader` when it loads a POM, and makes both checks use it, falling back to the validation level only when the flag is unset. @gnodet, does that work for the activation sandbox? Until it is released, an embedder can build its project at `VALIDATION_LEVEL_MAVEN_2_0`. Sylwester -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
