I can handle this, Erick (on the branch). In short, "assemble" is a task added by the "base" gradle plugin. This is just a placeholder for things that should be "assembled" in the project. The java plugin puts together a jar file from compiled classes, for example.
Gradle projects typically don't collect dependency jars anywhere (they suck them in from caches without copying whenever they're needed). We can copy them over though -- this is simple. D. On Sat, Nov 16, 2019 at 3:44 AM Erick Erickson <erickerick...@gmail.com> wrote: > > In a nutshell, it doesn’t look like there’s any task that populates: > > ../solr/server/solr-webapp/webapp/WEB-INF/lib/ > ../solr/server/lib/ext/ > ../solr/server/lib/ > > with jar files. So "solr/bin/solr start” simply can’t start since it defines > CLASSPATH to point to them. Before I try to mimic the Ant build that > populates these, should we re-think how these are populated and/or where they > live? > > “gradlew assemble” pulls the jars down, but I sure can’t find anywhere where > that task is defined, and the Gradle javadocs say things like: > > assemble() - Method in class org.gradle.language.assembler.tasks.Assemble > > Assemble - Class in org.gradle.language.assembler.tasks > Translates Assembly language source files into object files. > > so I haven’t a clue what’s up with that task. > > Thanks, > Erick > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
