[
https://issues.apache.org/jira/browse/SOLR-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044592#comment-13044592
]
Gabriele Kahlout commented on SOLR-2574:
----------------------------------------
{quoute} I'm not sure that is great behavior – the point of SLF4j to let people
choose what framework to use... {quote}
It'd make some sense if I'm re-building solrj, but as a client that (to me)
totally unacceptable. If slf4j is such a great thing, that's ! the way to
promote it, you get a build failure because of this slf4j and then go figure
out the 'simplest thing that could possible work'[Extreme Programming].
I'm ! alone with the issue, others have posted about it (I'm the one taking the
time to post an issue).
> Add SLF4J-nop dependency
> ------------------------
>
> Key: SOLR-2574
> URL: https://issues.apache.org/jira/browse/SOLR-2574
> Project: Solr
> Issue Type: Bug
> Reporter: Gabriele Kahlout
> Priority: Minor
> Fix For: 1.4
>
> Attachments: solrjtest.zip
>
>
> Whatever the merits of slf4j, a quick solrj test should work.
> I've attached a sample 1-line project with dependency on solrj-3.2 on run it
> prints:
> {code}
> java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
> at
> org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.<clinit>(CommonsHttpSolrServer.java:72)
> at com.mysimpatico.solrjtest.App.main(App.java:12)
> {code}
> Uncomment the nop dependency and it will work.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]