jira-importer commented on issue #559: URL: https://github.com/apache/maven-invoker-plugin/issues/559#issuecomment-2957801798
**[Tuomas Kiviaho](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tuomas_kiviaho)** commented Thanks for the clarification. My workaround was to switch from `invoker:install` to premature installing at `pre-integration-test` phase. If I recall correctly I stopped poking around when I saw that invoker did use shared metadata creation but had it's own rather crude implementation for it. Install plugin on the other hand didn't "corrupt" the local repo with such partial (this is the model 1.0.0 I presume) metadata and thus I was able to continue without too much of a fuzz. I'd close the issue by knowing now that the limitation had left it's marks/scars to the codebase. PS. IMO `invoker:install` might be worth looking at with pair of eyes that know more about the subtleties involved with metadata generation and resolving. -- 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
