lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriele Kahlout (JIRA)" <>
Subject [jira] [Commented] (SOLR-2537) Refactor Solr modules structure
Date Mon, 23 May 2011 13:16:47 GMT


Gabriele Kahlout commented on SOLR-2537:

I get a 403 error code when I follow this link:

{quote}   1. Can you explain why the workaround makes it impossible to add a dependency on
the Solr war? This makes no sense to me.{quote}
Sorry, I meant 'jar'. The project Solr Search Server (the one in solr/src/webapp which contains
EmbeddedSolrServer) is packaged as a war. But in a Solr plugin I need to depend on the class
files packaged in a jar. How do I do that? Attempts were mentioned here[1].

   2. is included in the solr-core jar - why not depend on this smaller
jar instead of the war?

When building it locally it won't work, probably because it's under the webapp project. Steps
to reproduce mentioned in the mlist[1]:

svn co -r 1104120 solr
cd solr; ant get-maven-poms; mvn -N -Pbootstrap install; mvn -DskipTests install
cd embeddedServerTest; mvn -X test


> Refactor Solr modules structure
> -------------------------------
>                 Key: SOLR-2537
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Gabriele Kahlout
>            Priority: Minor
>             Fix For: 3.1.1
> Solr modules are nested in a non-standard archeotype (e.g. Solr Core module is in the
src dir of Solr parent).
> Also, a workaround for avoiding maven dependencies between Solr Core and Testframework
makes it impossible to add a depenency on Solr-3.2-SNAPHOST (Solr Search Server) since it's
packaged as a war, to import, for example. It has been discussed on
the mailing list[1].
> I've, in the mlist, suggested to "create yet one more module for Tests which depend on
Solr Core and on the Test Framework. The org burden of that extra module, versus the ease
of building configuration, I believe, outweights."
> However I realize there's a major drawback in that, i.e. that Solr Core will build without
passing the tests in the other module. There're 2 solutions:
> 1. Make Solr Core a parent module that encompasses a thin Solr Core, the TestFramework
module, and the Tests-only module;
> 2. 'Downgrade' Testframework from being a fully-fledged module by moving the packages
under Solr Core. 
> 2a. Move them under Solr Core test packages.
> 2b. move them under Solr Core src
> To me 2a is most intuitive. Those that want a dependency on Solr TestFramework declare
it with <classifier>tests</classifier>, which packages only the tests, and the
Solr Core classes those require.[2][3]
> The same refactoring applies to lucuene.
> [1]
> [2]
> [3] I've successfully used it before.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message