You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/10/21 15:52:07 UTC

[GitHub] [maven-mvnd] gzm55 commented on pull request #717: Try native image then fallback to pure java version

gzm55 commented on PR #717:
URL: https://github.com/apache/maven-mvnd/pull/717#issuecomment-1287149373

   > These changes seem to be addressing what I'd call install time concerns. Whether the given build of mvnd native executable can run on the current machine can be decided once at install time. Why do we need to run all those checks anew on every invocation of mvnd?
   
   how about we do a persist optimization at the real installing time for each package manager? almost every package manager has a post installing step, in which we can check via `mvnd-native --status`, if passed, then `mv -f mvnd-native mvnd` to overwrite the generic entry script.


-- 
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-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org