rdicroce commented on PR #364: URL: https://github.com/apache/maven-resolver/pull/364#issuecomment-1814805054
I tested this on Windows and it does not fix the problem. The way I tested it was: 1. Build the #365 branch. 2. Replace all of the maven-resolver JARs in Eclipse's plugins\org.eclipse.m2e.maven.runtime_3.9.400.20230826-0755\jars directory by renaming the originals to have .orig on the end, and then changing the names of the built JARs to match the 1.9.14 filenames. I'm using Eclipse 2023-09. 3. Open a workspace containing project A. This project has a SNAPSHOT dependency on project B. 4. Open a second workspace containing project B. 5. Run a 'clean install' build of project B. I agree with @laeubi's assessment. If a file is open for any reason, it can't be replaced. At least, I've never heard of any way of doing it on Windows. Linux is a different story. -- 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
