@alexmiller i can't seem to be able to deploy tools.reader using the new jenkins:

[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.4.4:deploy (default-deploy) on project tools.reader: Execution default-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.4.4:deploy failed: A required class was missing while executing org.sonatype.plugins:nexus-staging-maven-plugin:1.4.4:deploy: org/sonatype/aether/version/InvalidVersionSpecificationException

see http://build.clojure.org/job/tools.reader/453/org.clojure$tools.reader/console

anything i need to update in my pom.xml?

Yeah, you'll need to update for the new infrastructure. Give me 5 minutes

no rush

ok, I just updated the pom to use the new parent pom

give it another try, hopefully that’s it

thanks!

yeah that did it. cheers

thanks for the heads up - I’m going to update all the other contribs similarly

all other contribs have been updated so should not have issues on next deploy

but of course, happy to figure it out if they do

Beyond updating to the new parent pom version, is there anything else needed to build .cljc files now?

(not that I’m planning .cljc files for clojure.java.jdbc of course… I’m just curious as to what’s involved)

I don’t think much else?

your clojure build will work as long as the cljc files are visible in the source dirs

and they will get included in the jar due to the same thing

maven builds are not currently doing anything with cljs, so as long as that is set up to include cljs in the src dirs and also to have some independent test process, seems like that should work

although data.xml is now doing cljs tests via nashorn, which might be something we should replicate

as that’s included in the actual maven test run and will fail the build as desired

Sounds good. Thanks @alexmiller I’m interested in this because I’m now maintaining Expectations and that is written as .cljc files and I’d like to have automated testing for the cljs half of the picture.