Hello, I'm experimenting with getting my feet wet with proper maven central releases by trying to get a small library[1] into maven central.
The sonatype instructions[2] require, among other things: (1) If the project packaging is jar, and the jar file contains java classes, there must be a -javadoc.jar for main artifact. (2) If the project packaging is jar, and the jar file contains java classes, there must be a -sources.jar for main artifact. It is non-obvious to me what to do about clojure projects. If I have *only* clojure code, and disable AOT in clojure-maven-plugin, I can address both (1) and (2) by no longer producing a jar that "contains java classes". However, that is not sustainable. Some projects may contain some Java code too, or else maybe AOT:ed clojure code (what is the idiomatic approach there btw; to AOT or not to AOT?). clojure-contrib *seems* to be using the strategy to just include .clj:s in the main artifact, although the clojure-contrib parent pom implies in comments that individual modules may over-ride the lack of AOT. How would such artifacts be accepted into maven central if they fail (1)/(2)? [1] https://github.com/scode/plru [2] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide -- / Peter Schuller -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
