[
https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926827#comment-16926827
]
Anshum Gupta commented on SOLR-13452:
-------------------------------------
Something strange that I guess only I have been hitting is the following error
when running *gw build*
{quote}*> Task :verifyLocks* FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':verifyLocks'.
> Found dependencies that were not in the lock state: [xml-apis:xml-apis].
> Please run './gradlew --write-locks'.
{quote}
Looking at the dependency tree, I see this:
{quote}
+--- xerces:xercesImpl -> 2.9.1
\--- xml-apis:xml-apis:1.3.04
{quote}
However, when checking the dependency tree, no on else sees the *xml-apis*
dependency, though the *xercesImpl* dependency exists for everyone. Any idea
about what might be going on here?
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -------------------------------------------------------------------------
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: gradle-build.pdf
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I took some things from the great work that Dat did in
> [https://github.com/apache/lucene-solr/tree/jira/gradle] and took the ball a
> little further.
>
> When working with gradle in sub modules directly, I recommend
> [https://github.com/dougborg/gdub]
> This gradle branch uses the following plugin for version locking, version
> configuration and version consistency across modules:
> [https://github.com/palantir/gradle-consistent-versions]
>
> https://github.com/apache/lucene-solr/tree/jira/SOLR-13452_gradle_6
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
