Replies: 1 comment 2 replies
-
|
Pomchecker is not responsible for this behavior, JReleaser is. It's possible to globally skip checking for sources and javadoc JARs when configured at the deployer level, instead of using Opening a JAR and checking its contents takes time. Also, there are JAR files that only contain resource files which I believe will still trigger the sources rule check performed by Maven Central. Thus that solution is not optional at the moment. This being said, I'll reach to Sonatype to find out more about the checks they perform on their side and see if they can be replicated by JReleaser. |
Beta Was this translation helpful? Give feedback.
-
Disabling globally may not be a good idea, since it would skip the cases where a JAR with classes should have produced its sources and javadoc correspondents. |
Beta Was this translation helpful? Give feedback.
-
|
Correct. Finding the exact checks applied to each artifact is key. For now is all of them (global) or explicit per artifact ( Having checks applied implicitly may be tricky but I can find out what's needed. |
Beta Was this translation helpful? Give feedback.
-
There are some JARs that contain only resources (and some are empty), thus it makes no sense to have a
-sourcesand a-javadocin these cases.My use case is a bit different, so using
artifactOverridesisn't an option here as I'm using a centralizedjreleaser.ymlwhich is invoked for deployment (https://github.com/quarkiverse/quarkiverse-release/blob/main/jreleaser.yml).Would it make sense if pomchecker checked if any
.classexists inside the JAR before requiring a-sourcesand-javadoc? IMHO that would be the only reason those would be needed.Beta Was this translation helpful? Give feedback.
All reactions