elharo commented on PR #3589: URL: https://github.com/apache/maven-surefire/pull/3589#issuecomment-6894840703
> I'm a bit sceptic changing a well known and old behaviour of surefire which is to generate report file such `TEST-fullpackagename.xml` . This gives quick access. eventually behind a configuration parameter. but frankly, it's been done this way for so long and without issue reported (except one) that i do not really want to break all tooling relying on this naming. That's a valid concern, but if I understand this PR it will only change file names that cannot currently fit on 255-character limit file systems. That is, anywhere this will change a filename, the current plygin fails completely. If that's incorrect, please elaborate. Even if that's so, I suppose we could change this PR so that it adjusts for the filesystem it's writing to, so it only truncates if it's on a file system that can't handle the longer name. That might allow us to support eCryptFS too. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
