[ https://issues.apache.org/jira/browse/SOLR-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037930#comment-13037930 ]
Gabriele Kahlout commented on SOLR-2537: ---------------------------------------- {quote} I get a 403 error code when I follow this link: http://dp4j.sourceforge.net/debug/SOLR-2537/ {quote} try http://dp4j.sourceforge.net/debug/SOLR-2537.zip {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]. {quote} 2. EmbeddedSolrServer.java is included in the solr-core jar - why not depend on this smaller jar instead of the war? {quote} When building it locally it won't work, probably because it's under the webapp project. Steps to reproduce mentioned in the mlist[1]: {code} svn co -r 1104120 http://svn.apache.org/repos/asf/lucene/dev/branches/branch_3x/ solr cd solr; ant get-maven-poms; mvn -N -Pbootstrap install; mvn -DskipTests install wget http://dp4j.sf.net/debug/embeddedServerTest.zip unzip embeddedServerTest.zip cd embeddedServerTest; mvn -X test {code} [1] http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201105.mbox/%3cbanlktinhw3vm9djgpvmsrwxhs8mwjoy...@mail.gmail.com%3e > Refactor Solr modules structure > ------------------------------- > > Key: SOLR-2537 > URL: https://issues.apache.org/jira/browse/SOLR-2537 > 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 > EmbeddedSolrServer.java, 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] > http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201105.mbox/%3c2d127f11dc79714e9b6a43ac9458147fbad42...@suex07-mbx-03.ad.syr.edu%3e > [2] http://maven.apache.org/guides/mini/guide-attached-tests.html > [3] I've successfully used it before. > https://code.google.com/p/memorizeasy/source/browse/MemoPlatform/persistenceui/pom.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org