HannesWell commented on PR #539: URL: https://github.com/apache/maven-resolver/pull/539#issuecomment-2301559183
> * the goal of supplier is to provide "baseline" only, and nothing in Resolver uses ENV variables I understand that. But the problem can be and that's why I encountered this at all, is that some artifacts cannot be resolved some system properties are missing. For example without any system-properties, org.apache.commons:commons-text:1.12.0 fails to resolve with a `ModelBuildingException` saying something like `[ERROR] Failed to determine Java version for profile`. In this case the `java.version` property is missing and e.g. the `animal-sniffer` profile from the `commons-parent` cannot determine if the activation element `<jdk>(,9)</jdk>` is met or not. And since properties and env-properties can also be used to activate profiles in general and profiles can contain additional dependencies, not having them can influence the resolution result. A general property activation will probably not fail the resolution if a property is missing (I haven't tested it), but the result would still be different than in a default maven installation. So the resolver could implicitly use env variablies. But I cannot tell if the latter already is already out of the scope of the baseline? -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
