lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stevo Slavic (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-1218) maven artifact for webapp
Date Mon, 20 Sep 2010 10:27:34 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912429#action_12912429
] 

Stevo Slavic commented on SOLR-1218:
------------------------------------

Voted for the issue too.

As a temporary workaround, to reference solr.war but still keep solr config files in IDE under
version control, I use following config:

{code:title=pom.xml|borderStyle=solid}
...
<plugin>
  <groupId>org.mortbay.jetty</groupId>
  <artifactId>jetty-maven-plugin</artifactId>
  <configuration>
    <stopPort>${jetty.stop.port}</stopPort>
    <stopKey>foo</stopKey>
    <webApp>${env.SOLR_HOME}/example/webapps/solr.war</webApp>
    <tempDirectory>${project.build.directory}/jetty-tmp</tempDirectory>
    <systemProperties>
      <systemProperty>
        <name>solr.solr.home</name>
        <value>${basedir}/src/main/solr/home</value>
      </systemProperty>
      <systemProperty>
        <name>solr.data.dir</name>
        <value>${project.build.directory}/solr/data</value>
      </systemProperty>
      <systemProperty>
        <name>solr_home</name>
        <value>${env.SOLR_HOME}</value>
      </systemProperty>
    </systemProperties>
  </configuration>
  <executions>
    <execution>
      <id>start-jetty</id>
      <phase>pre-integration-test</phase>
      <goals>
        <goal>deploy-war</goal>
      </goals>
      <configuration>
        <daemon>true</daemon>
        <webAppConfig>
          <contextPath>/solr</contextPath>
          <tempDirectory>${project.build.directory}/jetty-tmp</tempDirectory>
        </webAppConfig>
        <connectors>
          <connector implementation="org.eclipse.jetty.server.nio.SelectChannelConnector">
            <port>${jetty.http.port}</port>
          </connector>
        </connectors>
      </configuration>
    </execution>
    <execution>
      <id>stop-jetty</id>
      <phase>post-integration-test</phase>
      <goals>
        <goal>stop</goal>
      </goals>
    </execution>
  </executions>
</plugin>
...
{code}

And update the SOLR_HOME environment variable with move to new Solr installation/version.
This is easy for development environment, not for CI (Hudson). That's why solr.war on public
repo would be handy.

> maven artifact for webapp
> -------------------------
>
>                 Key: SOLR-1218
>                 URL: https://issues.apache.org/jira/browse/SOLR-1218
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 1.3
>            Reporter: Benson Margulies
>
> It would be convenient to have a <packaging>war</packaging> maven project
for the webapp, to allow launching solr from maven via jetty.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message