On Thu, 16 Apr 2026 at 15:21, Gary Gregory <[email protected]> wrote:
> Just FYI: > > https://github.com/siom79/japicmp/issues/504 > > Gary > Your bug report uses a git hash that is not recognised on my clone of the repo so you may have a typo. On the current 1.3-branch the command still breaks. But it breaks in the documentation module. This has no code. The jar artifact is empty and not released to Maven central. I presume japicmp cannot download a 1.2 version for comparison. The project must be a jar project in order to use the javadoc aggregate report goal. But japicmp should not be run here. I could add a japicmp.skip property to this module. But that would also apply to lots of other modules in the codebase (examples) that are also not released to Maven central. Better to just use the default maven goal which activates japicmp in the correct modules using a profile.
