jira-importer commented on issue #265: URL: https://github.com/apache/maven-jlink-plugin/issues/265#issuecomment-2629101475
**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** commented [Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte) Attached. I am expecting three things: 1. Consist ordering rules throughout all Maven plugins (e.g. compiler, jlink, etc): if the compiler will be passed modules in the same order mentioned by \<dependency> then I expect the first plugin to always win. 2. The same pom.xml file should always result in the same build/runtime behavior (deterministic behavior). If you guys are using HashMap or some other collection that does not guarantee order, we run the risk of getting a different modulepath ordering at every run. 3. Swapping the order of the dependencies should result in main() outputting "the other" plugin. So if you used to get "plugin1" as output, swapping dependencies should result in "plugin2" getting output. -- 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
