[
https://issues.apache.org/jira/browse/SOLR-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980832#comment-13980832
]
ASF subversion and git services commented on SOLR-6006:
-------------------------------------------------------
Commit 1589959 from [~steve_rowe] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1589959 ]
SOLR-6006: Separate test and compile scope dependencies in the Solrj and Solr
contrib ivy.xml files, so that the derived Maven dependencies get filled out
properly in the corresponding POMs (merged trunk r1589937, r1589940, and
r158953)
> Separate test and compile scope dependencies in the Solrj and Solr contrib
> ivy.xml files, so that the derived Maven dependencies get filled out properly
> in the corresponding POMs
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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]
