The new common module's POM had artifactId lucene-common instead of lucene-common-module, so generate-maven-artifacts failed to find the built jar when deploying.
I've committed a fix to the POM, generate-maven-artifacts succeeds for me locally. Steve > -----Original Message----- > From: Apache Jenkins Server [mailto:jenk...@builds.apache.org] > Sent: Saturday, June 25, 2011 10:25 AM > To: dev@lucene.apache.org > Subject: [JENKINS-MAVEN] Lucene-Solr-Maven-trunk #159: POMs out of sync > > Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/159/ > > No tests ran. > > Build Log (for compile errors): > [...truncated 9467 lines...] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org
