This message was deleted.
# community-support
s
This message was deleted.
p
Theoretically you can use the built in option to convert your project to maven first and then use the Gradle to maven converter provided by gradle init. But I guess, after using two converters you would still need to manually adopt some build code to have β€œcorrect” Gradle code. So you might give it a try but expect manual work too.
πŸ˜ƒ 1
f
Aha, right, that sounds like something can probably save me some (and perhaps a lot of) time, thank you very much πŸ™‚
p
It will you only save same time if the output is correct too πŸ€·πŸ»β€β™‚οΈ
πŸ˜… 1
f
It's quite a large project and the configurations are pretty messy, I double whether it can go that smooth or not haha πŸ˜›
I tried this on a very mini workspace with 2 projects, seem not working well... the maven pom.xml is generated but it has no dependency info generated at all...
t
You could probably write some tool to process your
.classpath
to Gradle build scripts as a base to declaring the dependencies (and source dirs probably); then yes do everything manually 🀷 (hundreds of projects, ouch! good luck!)
βœ… 1