[
https://issues.apache.org/jira/browse/SOLR-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107099#comment-15107099
]
Daniel Collins commented on SOLR-8567:
--------------------------------------
[~erickerickson] The references to 5.4 was my bad, I'm back-porting to our
internal 5.4.x branch which was what confused me, so apologies for that. I've
updated my comment now to correct that.
The only versions that are broken are 5.5 and trunk, so only "unreleased"
branches.
I wonder if anyone (else) used the Maven build process, wasn't sure of its
status, but I figured it wasn't really used much. For any projects which are
dependent on Lucene (e.g. Luwak), maven seems to be a more convenient build
mechanism, so we do make use of it, but I don't know who else does!
> SOLR-839 broke the Maven build (trunk, 5.5)
> -------------------------------------------
>
> Key: SOLR-8567
> URL: https://issues.apache.org/jira/browse/SOLR-8567
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: 5.5, Trunk
> Reporter: Daniel Collins
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-8567.patch
>
>
> SOLR-839 adds a new code dependency between the Solr test code and the Lucene
> test code. ant handles this with some updates to the common-build.xml
> (included in SOLR-839) but the maven build mechanism needs updates to the
> pom.xml.template with an equivalent change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
