I have a maven project that I had converted it to gradle using the command gradle init in the IDE intellij.
The conversation was successful but then for some reason I decided to remove all the gradle files including gradle.build and did gradle init again and this time gradle.build is not created. I tried to delete the catch files in .gradle in location C in windows it didn’t help also tried “invalidated and clear catches” in IDE intellij same issue.
Please look over your post and correct it.
You provide extremely blurry information, that way it is extremely hard to guess what might be your problem.
For example do you mean “cache” when you say “catch”?
gradle.init and gradle.build are not a thing, but maybe you mean build.gradle?
…?
Also, what happens if you do the command now, what is the output?
Can you share the build --scan URL of your unsuccessful try?
My bad I mistyped yes I meant build.gradle and by catched I meant cache
Here is the output using the command line gradle init –scan
PS C:\Users\DANIIL\Downloads\EFFECTIVE_MOBILE_PROJECTS\part 4\CsvWriter> gradle init --scan
Calculating task graph as no cached configuration is available for tasks: init
An internal error occurred that prevented a Build Scan from being created.
Please report this via https://github.com/gradle/gradle/issues
Found a Maven build. Generate a Gradle build from this? (default: yes) [yes, no] yes
Select build script DSL:
1: Kotlin
2: Groovy
Enter selection (default: Kotlin) [1..2] 1
Generate build using new APIs and behavior (some features may change in the next minor release)? (default: no) [yes, no] yes
> Task :init
> Maven to Gradle conversion is an incubating feature.
> For more information, please refer to https://docs.gradle.org/9.3.1/userguide/migrating_from_maven.html in the Gradle documentation.
BUILD SUCCESSFUL in 12s
1 actionable task: 1 executed
Configuration cache entry stored
As you seen in the output, the --scan did not work and Gradle asked you to report an issue about it, so please do. Only issues that are reported have a chance to get fixed.
The output though seems to be fine and telling the conversion was successful.
So what’s the problem then?
If you say that with that output you did not get get build scripts, that sounds like you should report another bug to Gradle.