After adding:
<build-directory>target</build-directory>
the war file is put into the target subdir.
On a side note:
running solr with maven jetty plugin seem to work, which required two
artifacts (couldn't figure out where does jetty store the lib dir in this
mode):
command. mvn jetty:run-war
(configured in the jetty-maven-plugin):
<dependencies>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.0.13</version>
</dependency>
<dependency>
<groupId>tomcat</groupId>
<artifactId>commons-logging</artifactId>
<version>4.0.6</version>
</dependency>
</dependencies>
when starting the webapp, however, solr tries to create a collection1:
17:02:53.108 [coreLoadExecutor-3-thread-1] INFO
org.apache.solr.core.CoreContainer - Creating SolrCore 'collection1' using
instanceDir: ${top-level}/solr/example/solr/collection1
Apparently, ${top-level} var isn't defined either.
On 19 June 2013 16:25, Dmitry Kan <[email protected]> wrote:
> also: ${build-directory} is not set anywhere in the project.
>
>
> On 19 June 2013 16:23, Dmitry Kan <[email protected]> wrote:
>
>> Hello,
>>
>> executing 'package' on Apache Solr Search Server pom
>> (maven-build/solr/webapp/pom.xml) puts the webapp into a null sub-directory.
>>
>> Apache Maven 3.0.4
>> OS: Ubuntu 12.04 LTS
>>
>> Thanks,
>>
>> Dmitry Kan
>>
>
>
