[
https://issues.apache.org/jira/browse/SOLR-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-6006:
-----------------------------
Attachment: SOLR-6006-contribs.patch
I neglected to test the Solr contribs, and they were failing after I committed
the patch on trunk because they all have a test-scope dependency on
jcl-over-slf4j - Uwe's Jenkins has made its unhappiness known:
[http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/10156/]
This patch fixes the build by giving each Solr contrib a {{test-lib/}} if it
doesn't already have it, and adding jcl-over-slf4j to its test scope
dependencies.
Committing shortly.
> Separate test and compile scope dependencies in the Solrj ivy.xml file, so
> that the derived Maven dependencies get filled out properly in the Solrj POM
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6006
> URL: https://issues.apache.org/jira/browse/SOLR-6006
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.7.2
> Reporter: Steven Scott
> Priority: Minor
> Attachments: SOLR-6006-contribs.patch, SOLR-6006.patch
>
>
> I'm not sure what version this first appeared in, as we just bumped from 4.5
> to 4.7, but log4j is specified as a dependency in the solr-solrj pom.xml, and
> without the optional flag. I checked out the source to verify that there
> isn't actually a dependency on log4j (doesn't seem to be), but I wasn't able
> to decipher the ant build (looks like there's a pom.xml.template that
> generates the pom with dependencies coming from Ivy?)
> Anyway, this is an issue since now we have to manually <exclude> log4j from
> every project that depends on SolrJ.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
