jira-importer commented on issue #640: URL: https://github.com/apache/maven-invoker-plugin/issues/640#issuecomment-2957810503
**[Christopher Tubbs](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ctubbsii)** commented I'm using `<cloneProjectsTo>${project.build.directory}/it</cloneProjectsTo>` in my particular use case. However, that does not solve the problem. The problem occurs because the **invoked** project (the one cloned) is running plugins which do not recognize the `build.log` file created in that project's root. Ensuring the invoked project is cloned to the invoking project's target directory only addresses the issue of confused plugins running on the invoking project, but that's not what is being described here. What is being described here is plugins running in the **invoked** project. -- 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
