Jitpack for v4.1.0 is broken

[esuomi]

Describe the bug

See jitpackProblem.txt
Note the original post gave this link: https://jitpack.io/com/github/MobilityData/gtfs-validator/v4.1.0/build.log this log was overwritten by a successful build since then. See the above attached file instead.

Looking at Jitpack's logs, the two main issues are missing documentation for various params and return values and no test artifacts, which together cause the build to fail in such way that nothing is published.

Steps/Code to Reproduce

• Click "Get It" on https://jitpack.io/#MobilityData/gtfs-validator for v4.1.0
• Wait for ages
• build is broken

Expected Results

Working build so that I could use gtfs-validator's latest&greatest as Maven dependency.

Actual Results

No artifact available.

Screenshots

No response

Files used

No response

Validator version

4.1.0

Operating system

unrelated

Java version

No response

Additional notes

No response

[welcome]

Thanks for opening your first issue in this project! If you haven't already, you can join our slack and join the #gtfs-validators channel to meet our awesome community. Come say hi 👋!

Welcome to the community and thank you for your engagement in open source! 🎉

[miles-grant-ibigroup]

We are facing the same issue, and are also unable to upgrade the package version as a result

[jcpitre]

Removed the failed build on jitpack (https://jitpack.io/#MobilityData/gtfs-validator) then did a build on a local test project and jitback rebuilt it with no error. It should now be available.

As to why it failed before and not now, I have some theories:

• I suspect the problem comes from aggregateJavadocJar tries to create Javadoc jar with abnormally huge file size freefair/gradle-plugins#640. One of the logs for the failed build said:

Execution failed for task ':aggregateJavadocJar'.
Could not add file '/home/jitpack/build/build/docs/aggregateJavadoc/gtfs-validator-4.1.0-javadoc.jar' to ZIP '/home/jitpack/build/build/docs/aggregateJavadoc/gtfs-validator-4.1.0-javadoc.jar'.

i.e. it was trying to add a jar file to itself. This fits with the bug.

• There was a change done in freefair that could have solved the problem, although I am not sure it affected the version we use: freefair/gradle-plugins@1ac0180

• Another possibility is that jitpack changed something in the way they build. In particular it seems that the freefair bug occurs on some linux distros, but not others. Maybe they changed the distro they use for building? Or some other change on their end.

• on the gtfs-validator side, it's building from v4.1.0 tag, so there was no change that could explain why it was broken but not anymore.

[jcpitre]

For reference I attached the log of the failed build here, since it was overwritten when the new successful build was done.
jitpackProblem.txt