[ 
https://issues.apache.org/jira/browse/SOLR-13452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835260#comment-16835260
 ] 

Mark Miller commented on SOLR-13452:
------------------------------------

[~caomanhdat], thanks for starting this! Picking things out of your gradle 
branch was invaluable.
 * I've got the overall build and test stuff behaving decently.
 * I have not done anything with dist packaging or maven publishing.
 * The build checks with Forbidden API's is probably going to be commented out 
for the moment - I've been running into issues where it seems to scan 3rd party 
libs, have not had a chance to dig or see if it was related to other resolved 
issues.
 * I try to mostly avoid compile and testCompile as they are deprecated (along 
with runtime) - so I use implementation and api, but without much thought as of 
now, so favoring implementation.
 * I got eclipse working fairly well for me, I don't use idea though, so I 
imagine some work there.
 * I've done some early regenerate stuff, but more to do, plus targets for 
downloading artifacts for some modules.
 * Still a lot to do! But not as much as there once was.

> 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
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build
>            Reporter: Mark Miller
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to