This should be fixed by my commit for LUCENE-5322 - I can no longer reproduce the problem locally.
On Fri, Nov 1, 2013 at 12:23 PM, Steve Rowe <sar...@gmail.com> wrote: > The problem here is that the copied/filtered solr-core POM is missing a > lot of dependencies: log4j, noggit, commons-io, httpcomponents. These are > added to the solr-core “classpath” in the Ant build from solrj and example > lib/ directories. When these are collected from the Ant build in > preparation for filtering the POMs, only files that actually exist make it > into the “classpath”, and apparently at the point the solr-core “classpath” > is examined, there is nothing in the solrj/lib/ and example/lib/ > directories. > > I can reproduce this locally, if I first "rm -rf $(find . -name ‘*.jar’)", > like the Jenkins build does. Looks like when “generate-maven-artifacts” > calls “filter-pom-templates”, it doesn’t invoke “resolve” (unlike > “get-maven-poms”, which does). Fix should be simple - I’ll work on it > later today. > > Steve > > On Oct 31, 2013, at 10:50 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > > > Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1015/ > > > > All tests passed > > > > Build Log: > > [...truncated 36479 lines...] > > [mvn] [INFO] > ------------------------------------------------------------- > > [mvn] [INFO] > ------------------------------------------------------------- > > [mvn] [ERROR] COMPILATION ERROR : > > [mvn] [INFO] > ------------------------------------------------------------- > > > > [...truncated 593 lines...] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > >
