New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOLR-13452: Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle. #972
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…uild) to Gradle. This a first rough commit, taking many things from Dat's gradle branch.
…java.naming.* could not be found.
…the point publishToLocalMaven works for simple jars.
…mespace module again.
… .settings and .out eclipse/gralde folders.
…ngs are used, breaking the build.
…sing finalizedBy.
… regenerate task.
… the default is to not even show what tasks executed.
…bout lack of input/output annotations on fields.
…ark/work and benchmark/temp as the file sizes and counts in those folders can make eclipse unhappy.
…ran config into their own files as well to simplify the main build.gradle.
…; TODO: on checking fails on all modifications
…ble forbidden apis check.
…tions, which was added for the javadoc task.
…ndencyInsight, but works across projects vs forcing you to hunt a project at a time.
…tarting config in ~/.gradle/gradle.properties.
…sing of tests.* properties via -P, documentation.
* We are incorrectly overriding our projects default directory based name - this really had the project in a whacky state. * Fix tests, we could no longer read classes from other projects. * Move build and build-eclipse to the root level instead of per project, making them easier to navigate and treat specially. * Look for user property overrides in user.properties in both the project root dir and the user home directory. * Some other minor fixes and cleanup.
Small delay - I have to review all this and spend some time with the standard build on this branch. |
…uild) to Gradle. Updated dependencies and created parallel license directories (Lucene and Solr) to handle 'jar-checksum' and 'jarChecksum' thrashing
…idoctor-ant from versions.props.
…ependency for which the license is missing.
…ally from a simple list and leave help/*.txt an uncluttered list of plain text help files.
…farkhaja:java-semver=0.9.0) that came in in the recent merge of master
…master. This is hacked around in configure-test.gradle (much like in ant).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Please provide a short description of the changes you're making with this pull request.
Solution
Please provide a short description of the approach taken to implement your solution.
Tests
Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.
Checklist
Please review the following and check all that apply:
master
branch.ant precommit
and the appropriate test suite.