Thanks for the suggestion. Adding .locks to .gitignore does not help. The error is the same.
Am Di., 28. Juli 2026 um 13:49 Uhr schrieb Greg Chabala < [email protected]>: > Sounds like a bug, Windows may be less tested than other platforms. > > Would it work if you added .locks to your .gitignore file? Sometimes that's > enough to hide a file from a plugin. > > > On Tue, Jul 28, 2026, 12:16 AM Andreas Kuhtz <[email protected]> > wrote: > > > Hello, > > > > I noticed that central-publishing-maven-plugin breaks with Maven > > 3.10.0-rc-1 under Windows because of .locks generated in the > > target/central-* directories. > > > > > > > ----------------------------------------------------------------------------------------- > > [INFO] --- central-publishing:0.11.0:publish > (injected-central-publishing) > > @ vldocking --- > > [INFO] Using Central baseUrl: https://central.sonatype.com > > [INFO] Using credentials from server id central in settings.xml > > [INFO] Staging 11 files > > > > > > [ERROR] > > > > Deployment fb7a5fc0-976f-447d-8833-9ad63218fd46 failed > > common: > > - Bundle has content that does NOT have a .pom file: > > org/bidib/jbidib/com/vldocking/vldocking, .locks > > > > > ----------------------------------------------------------------------------------------- > > > > I don't know if this is a known issue, but I have not found anything when > > searching. > > Going back to 3.9.16 solved the issue for me. > > > > Thank you, > > Andreas > > >
