arturobernalg commented on issue #13395: URL: https://github.com/apache/maven/issues/13395#issuecomment-6096367294
I tried to reproduce this on current master (`61f92e956c`). The profile activation issue does not reproduce: with `VALIDATION_LEVEL_MINIMAL`, both user-property and file-activated profiles are applied. `build(File, ...)` uses a source with a null model id, so it is not treated as external by the profile activation sandbox. There is, however, a related problem. A standalone `ProjectBuilder.build(File, ...)` with a local `../pom.xml` parent fails at MINIMAL validation: - MINIMAL + processPlugins=true: local parent not resolved - MINIMAL + processPlugins=false: local parent not resolved - STRICT + processPlugins=true: local parent resolved - STRICT + processPlugins=false: local parent not resolved The bridge currently selects `BUILD_EFFECTIVE` only for `STRICT + processPlugins`. As a result, `processPlugins` / validation level also determine whether local-parent lookup and other build-project semantics are enabled. Simply switching these calls to `BUILD_EFFECTIVE` does not look correct either, because that would also force strict validation and ignore the validation level requested through the v3 API. It seems the underlying question is whether project/build semantics and validation strictness need to be represented independently in the Maven 4 model builder. Would you prefer this to be addressed as part of #13395, or should the local-parent behavior be tracked separately before changing the model-builder API? -- 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]
