[
https://issues.apache.org/jira/browse/LUCENE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178303#comment-17178303
]
Erick Erickson commented on LUCENE-9433:
----------------------------------------
What's the approach we're going to use here?
I've poked around a bit and there's ant.importBuild which we might be able to
carve out of the current Ant eclipse task and run, although that seems more
than a little hackish.
We could try to translate the eclipse target from ant into "gradle friendly"
work.
Meanwhile, this is holding up this Jira and I'd like to see what I can do to
nudge it along.
> Remove Ant support from trunk
> -----------------------------
>
> Key: LUCENE-9433
> URL: https://issues.apache.org/jira/browse/LUCENE-9433
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Items that may need to be addressed:
> * -Testing with OpenJDK early access releases-
> * Mavenizing
> * Test speed (?)
> * -Update any mentions of ant in the ref guide- (on EOE fork)
> * Update Confluence, in particular "how to contribute"
> * Update Jenkins to not try to run ant anything
> * make an eclipse task (netbeans too?)
> * -various documentation (e.g. README/INSTALL) files still needs to be
> converted to gradle- (on EOE fork)
> * fix some relative links in javadocs which contain ant module names
> * dev-tools/scripts/* There are a lot of mentions of ant in the *.py* files,
> and some in the README.md. This one should probably be its own JIRA since
> it'll require quite a bit of verification...
> * Make "the best damn beasting script in the world" work with the Gradle
> build.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
