Elliotte Rusty Harold

Upgrading to PMD 7.12 did not fix the problem. You can see it around commit 066d1a4ee8c02aa84f09f7c2740b6b797d239f3c in https://github.com/apache/maven-pmd-plugin/pull/192 though you might have to dig in with the debugger to see...

Digging into the CPD code this doesn't look like an intentional catch of the runtime exception. Rather it's an accidental catch because SourceManager's close method is declared to throw a...

Do we generally include dependency upgrades in release notes? This should be even more transparent to end users than an API change, which we don't usually mention.

Most PRs don't get release notes, including most PRs that break the Java API. Release notes seem to be used only for changes that appear to an end user, which...

That is true, but that is an implementation detail. There's nothing in this class or API that indicates it should depend on which file system providers are installed. And this...

That's not quite accurate. Java versions 1 and up do support HTTP. They just don't support it as a file system since it really isn't a file system. Neither are...

@rschlussel Don't merge, but if you get around to looking for the bug we discussed on Tuesday, you might find this helpful or at least give you a few ideas...

If we can make pomless work, great; but one way or another I do want to reduce the friction of changing our version numbers.

You've pointed to existing bad API design. getFullPathNoEndSeparator("C:") should return "" if the argument is a Unix path and "C:" if that path is a Windows path. Of course, it's...

Tests failed: Running post-build script: /home/runner/work/maven-dependency-plugin/maven-dependency-plugin/target/it/mdep-779-analyze-only-verbose-shows-class-names/verify.bsh java.lang.Exception: Expected warning missing at java.base/jdk.internal.reflect.NativeConstructorAcc