[
https://issues.apache.org/jira/browse/SOLR-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256860#comment-13256860
]
Ryan McKinley commented on SOLR-3358:
-------------------------------------
yes, solr classpath is a disaster! I agree with everything you say/suggest, i
figured this was the tradeoff for avoiding maven
The other thing to consider is a test classpath -- the only class that uses
jetty in the src tree is JettySolrRunner. I think that could be moved to test.
re SpellChecker in solrj. The maven build should fail if you do this since it
does use different classpaths for each module. (not a real solution, but just
pointing it out)
As a first step, I think we should remove the single solr/lib folder and
replace it with:
solrj/lib
core/lib
core/lib-test (includes jetty)
webapp/lib (has the slf4j-over stuff)
> Capture Logging Events from JUL and Log4j
> -----------------------------------------
>
> Key: SOLR-3358
> URL: https://issues.apache.org/jira/browse/SOLR-3358
> Project: Solr
> Issue Type: New Feature
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Attachments: SOLR-3358-compile-path.patch, SOLR-3358-logging.patch,
> SOLR-3358-logging.patch
>
>
> The UI should be able to show the last few log messages. To support this, we
> will need to register an Appender (log4j) or Handler
> (JUL) and keep a buffer of recent log events.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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
