[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated LUCENE-9475:
---
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** -Remove all of dev-tools/maven?-
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}-
* -Remove obsolete files in root dirs of lucene and solr (like
ivy-versions.props, now integrated into gradle)-
* -Remove Maven build files (obsolete with Gradle)-
* Hoss's test rollups?
* -Enable javadocs after ant stops being used (LUCENE-9441)-
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* -Clean up anything in lucene/tools-
* Clean up Confluence, in particular any page that mentions IDEs. The "How to
Contribute" page has several links to various bits and pieces of how to use
IDEs, and some mention ant.
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} -
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
* Clean up Confluence, in particular any page that mentions IDEs. The "How to
Contribute" page has several links to various bits and pieces of how to use
IDEs, and some mention ant.
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 release which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** -Remove all of dev-tools/maven?-
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference guide build works under
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-9475:
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} -
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
* Clean up Confluence, in particular any page that mentions IDEs. The "How to
Contribute" page has several links to various bits and pieces of how to use
IDEs, and some mention ant.
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part of
post-ant cleanup, I'll do it).
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
* Clean up Confluence, in particular any page that mentions IDEs. The "How to
Contribute" page has several links to various bits and pieces of how to use
IDEs, and some mention ant.
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 release which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated LUCENE-9475:
---
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part of
post-ant cleanup, I'll do it).
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
* Clean up Confluence, in particular any page that mentions IDEs. The "How to
Contribute" page has several links to various bits and pieces of how to use
IDEs, and some mention ant.
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part of
post-ant cleanup, I'll do it).
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 release which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference guide build works under Gradle-
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> *
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated LUCENE-9475:
---
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 release which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part of
post-ant cleanup, I'll do it).
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part of
post-ant cleanup, I'll do it).
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 release which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference guide build works under Gradle-
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part
> of post-ant cleanup, I'll do it).
> * Remove obsolete files in root dirs of lucene and solr (like
>
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-9475:
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part of
post-ant cleanup, I'll do it).
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference guide build works under Gradle-
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * -Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}} - (this is part
> of post-ant cleanup, I'll do it).
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Remove Maven build
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-9475:
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.- (see LUCENE-9465, LUCENE-9472 for alternatives)
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference guide build works under Gradle-
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Remove Maven build files (obsolete with Gradle)
> * Hoss's test rollups?
> * Enable javadocs after ant stops being used (LUCENE-9441)
> * fix some relative links in javadocs
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett updated LUCENE-9475:
--
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* -Verify reference guide build works under Gradle-
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * -Verify reference guide build works under Gradle-
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Remove Maven build files (obsolete with Gradle)
> * Hoss's test rollups?
> * Enable javadocs after ant stops being used (LUCENE-9441)
> * fix some relative links in javadocs which contain ant module names (?)
> *
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated LUCENE-9475:
---
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
*
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.
* Update the release documentation to reflect Gradle (LUCENE-9488)
* Clean up anything in lucene/tools
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.
* Update the release documentation to reflect Gradle (LUCENE-9488)
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> *
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * Verify reference guide build works under Gradle
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Remove Maven build files (obsolete with Gradle)
> * Hoss's test rollups?
> * Enable javadocs after ant stops being used (LUCENE-9441)
> * 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.
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated LUCENE-9475:
---
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven. See
LUCENE-9077 (Dawid)
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* -Move Jenkins over to use Gradle only-
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
* 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.
* Update the release documentation to reflect Gradle (LUCENE-9488)
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven.
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* Move Jenkins over to use Gradle only
** Nightlies
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven. See
> LUCENE-9077 (Dawid)
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * -Move Jenkins over to use Gradle only-
> * Verify reference guide build works under Gradle
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Remove Maven build files (obsolete with Gradle)
> * Hoss's test rollups?
> * Enable javadocs after ant stops being used (LUCENE-9441)
> * 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.
> * Update the release documentation to reflect Gradle (LUCENE-9488)
--
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:
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-9475:
--
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven.
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* Move Jenkins over to use Gradle only
** Nightlies
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Remove Maven build files (obsolete with Gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven.
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* Move Jenkins over to use Gradle only
** Nightlies
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven.
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * Move Jenkins over to use Gradle only
> ** Nightlies
> * Verify reference guide build works under Gradle
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Remove Maven build files (obsolete with Gradle)
> * Hoss's test rollups?
> * Enable javadocs after ant stops being used (LUCENE-9441)
--
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
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[
https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-9475:
--
Description:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven.
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* Move Jenkins over to use Gradle only
** Nightlies
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
* Remove obsolete files in root dirs of lucene and solr (like
version.properties, now integrated into gradle)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
was:
Once the bulk of the Ant build system is removed, stuff will come bubbling up
out of the cracks, especially as we try the first 9.0 build which will be
Gradle only. Here we list some of the areas we'll have to be aware of. Please
add as you see fit. Assigning to myself to track, but I certainly don't want
hog all the fun.
* Remove Maven support and replace with "The Gradle Way" of doing Maven.
** Remove all of dev-tools/maven?
** Other dev-tools files no longer used, check if any Gradle build file
references and remove if not.
* Move Jenkins over to use Gradle only
** Nightlies
* Verify reference guide build works under Gradle
* Smoke tester
* Remove anything having to to with Clover (obsolete as of Java 11)
* Hoss's test rollups?
* Enable javadocs after ant stops being used (LUCENE-9441)
> Enhance the Gradle build as necessary after removing Ant support
>
>
> Key: LUCENE-9475
> URL: https://issues.apache.org/jira/browse/LUCENE-9475
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
>Affects Versions: master (9.0)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Major
>
> Once the bulk of the Ant build system is removed, stuff will come bubbling up
> out of the cracks, especially as we try the first 9.0 build which will be
> Gradle only. Here we list some of the areas we'll have to be aware of. Please
> add as you see fit. Assigning to myself to track, but I certainly don't want
> hog all the fun.
> * Remove Maven support and replace with "The Gradle Way" of doing Maven.
> ** Remove all of dev-tools/maven?
> ** Other dev-tools files no longer used, check if any Gradle build file
> references and remove if not.
> * Move Jenkins over to use Gradle only
> ** Nightlies
> * Verify reference guide build works under Gradle
> * Smoke tester
> * Remove anything having to to with Clover (obsolete as of Java 11)
> * Remove all of {{lucene/tools}} (Ivy, forbiddenapis,...}}
> * Remove obsolete files in root dirs of lucene and solr (like
> version.properties, now integrated into gradle)
> * Hoss's test rollups?
> * Enable javadocs after ant stops being used (LUCENE-9441)
--
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
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[ https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated LUCENE-9475: --- Description: Once the bulk of the Ant build system is removed, stuff will come bubbling up out of the cracks, especially as we try the first 9.0 build which will be Gradle only. Here we list some of the areas we'll have to be aware of. Please add as you see fit. Assigning to myself to track, but I certainly don't want hog all the fun. * Remove Maven support and replace with "The Gradle Way" of doing Maven. ** Remove all of dev-tools/maven? ** Other dev-tools files no longer used, check if any Gradle build file references and remove if not. * Move Jenkins over to use Gradle only ** Nightlies * Verify reference guide build works under Gradle * Smoke tester * Remove anything having to to with Clover (obsolete as of Java 11) * Hoss's test rollups? * Enable javadocs after ant stops being used (LUCENE-9441) was: Once the bulk of the Ant build system is removed, stuff will come bubbling up out of the cracks, especially as we try the first 9.0 build which will be Gradle only. Here we list some of the areas we'll have to be aware of. Please add as you see fit. Assigning to myself to track, but I certainly don't want hog all the fun. * Remove Maven support and replace with "The Gradle Way" of doing Maven. ** Remove all of dev-tools/maven? ** Other dev-tools files no longer used, check if any Gradle build file references and remove if not. * Move Jenkins over to use Gradle only ** Nightlies * Verify reference guide build works under Gradle * Smoke tester * Remove anything having to to with Clover (obsolete as of Java 11) * Hoss's test rollups? > Enhance the Gradle build as necessary after removing Ant support > > > Key: LUCENE-9475 > URL: https://issues.apache.org/jira/browse/LUCENE-9475 > Project: Lucene - Core > Issue Type: Improvement > Components: general/build >Affects Versions: master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > Once the bulk of the Ant build system is removed, stuff will come bubbling up > out of the cracks, especially as we try the first 9.0 build which will be > Gradle only. Here we list some of the areas we'll have to be aware of. Please > add as you see fit. Assigning to myself to track, but I certainly don't want > hog all the fun. > * Remove Maven support and replace with "The Gradle Way" of doing Maven. > ** Remove all of dev-tools/maven? > ** Other dev-tools files no longer used, check if any Gradle build file > references and remove if not. > * Move Jenkins over to use Gradle only > ** Nightlies > * Verify reference guide build works under Gradle > * Smoke tester > * Remove anything having to to with Clover (obsolete as of Java 11) > * Hoss's test rollups? > * Enable javadocs after ant stops being used (LUCENE-9441) -- 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
[jira] [Updated] (LUCENE-9475) Enhance the Gradle build as necessary after removing Ant support
[ https://issues.apache.org/jira/browse/LUCENE-9475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Erickson updated LUCENE-9475: --- Description: Once the bulk of the Ant build system is removed, stuff will come bubbling up out of the cracks, especially as we try the first 9.0 build which will be Gradle only. Here we list some of the areas we'll have to be aware of. Please add as you see fit. Assigning to myself to track, but I certainly don't want hog all the fun. * Remove Maven support and replace with "The Gradle Way" of doing Maven. ** Remove all of dev-tools/maven? ** Other dev-tools files no longer used, check if any Gradle build file references and remove if not. * Move Jenkins over to use Gradle only ** Nightlies * Verify reference guide build works under Gradle * Smoke tester * Remove anything having to to with Clover (obsolete as of Java 11) * Hoss's test rollups? was: Once the bulk of the Ant build system is removed, stuff will come bubbling up out of the cracks, especially as we try the first 9.0 build which will be Gradle only. Here we list some of the areas we'll have to be aware of. Please add as you see fit. Assigning to myself to track, but I certainly don't want hog all the fun. * Remove Maven support and replace with "The Gradle Way" of doing Maven. ** Remove all of dev-tools/maven? ** Other dev-tools files no longer used, check if any Gradle build file references and remove if not. * Move Jenkins over to use Gradle only ** Nightlies * Verify reference guide build works under Gradle * Smoke tester * Remove anything having to to with Clover (obsolete as of Java 11) > Enhance the Gradle build as necessary after removing Ant support > > > Key: LUCENE-9475 > URL: https://issues.apache.org/jira/browse/LUCENE-9475 > Project: Lucene - Core > Issue Type: Improvement > Components: general/build >Affects Versions: master (9.0) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Major > > Once the bulk of the Ant build system is removed, stuff will come bubbling up > out of the cracks, especially as we try the first 9.0 build which will be > Gradle only. Here we list some of the areas we'll have to be aware of. Please > add as you see fit. Assigning to myself to track, but I certainly don't want > hog all the fun. > * Remove Maven support and replace with "The Gradle Way" of doing Maven. > ** Remove all of dev-tools/maven? > ** Other dev-tools files no longer used, check if any Gradle build file > references and remove if not. > * Move Jenkins over to use Gradle only > ** Nightlies > * Verify reference guide build works under Gradle > * Smoke tester > * Remove anything having to to with Clover (obsolete as of Java 11) > * Hoss's test rollups? -- 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
