[
https://issues.apache.org/jira/browse/DATAFU-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024783#comment-18024783
]
Kamal Dallasheh commented on DATAFU-183:
----------------------------------------
Hi @eyalallweil,
I've fixed the immediate CI errors by using the project's Gradle wrapper
(8.14.3)
instead of the system Gradle 9.1.0. This resolves the "Unknown command-line
option" errors.
However, I want to make sure I'm addressing your requirements correctly.
Would you prefer:
**Option A:** Keep the current fix (using Gradle 8.14.3) - works now,
quick solution
**Option B:** Upgrade the project to Gradle 9.x properly - modernize
the codebase for future compatibility, remove all deprecated options
I'm ready to implement either approach. Which direction would you like me
to take?
Thanks!
> Fix GitHub Actions CI
> ---------------------
>
> Key: DATAFU-183
> URL: https://issues.apache.org/jira/browse/DATAFU-183
> Project: DataFu
> Issue Type: Task
> Affects Versions: 2.1.0
> Reporter: Eyal Allweil
> Priority: Major
> Labels: GoodForNewContributors, gradle, newbie, up-for-grabs
>
> The GitHub Actions CI is now failing when trying to run
> {code:java}
> gradle -b bootstrap.gradle{code}
> with this error:
> {noformat}
> Unknown command-line option '-b'.
> {noformat}
> This is probably a problem caused by an upgrade to Gradle 9.0.0 (previously
> 8.14.3 was being used)
>
> We need to either fix the GitHub action or our build so our CI can run. One
> way to test/debug this is to fork the repo and modify the forked version of
> the action (for example in the file
> [test.yaml|https://github.com/apache/datafu/blob/main/.github/workflows/tests.yml])
> It appears that one fix is to use some newer [Gradle
> Wrapper|https://docs.gradle.org/current/userguide/gradle_wrapper.html]
> functionality rather than what we are currently doing in our [bootstrap
> file|https://github.com/eyala/datafu/blob/main/bootstrap.gradle].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
