fix(java): move code to src folder APIC-411

[millotp]

🧭 What and Why

🎟 JIRA Ticket: APIC-411

In preparation for the java release, move the code to src folder to have it's own build.gradle file.

Changes included:

• Move src

🧪 Test

CI

[netlify]

✅ Deploy Preview for api-clients-automation canceled.

Name	Link
🔨 Latest commit	69c964f
🔍 Latest deploy log	https://app.netlify.com/sites/api-clients-automation/deploys/626114bc634fdf0008acb71f

[algolia-bot]

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.

[shortcuts]

Could we do this PR on top of #385 so it uses the next logic in place? 😇

[millotp]

#385 will need rebasing and it will be a mess, I will make the changes once it's merged

[shortcuts]

This looks good! I just have one question: Is the other src folder usable or do we need the algoliasearch-core one?

[millotp]

Actually everything should be inside algoliasearch-core/src/ now, should I delete the files by hand ?

[shortcuts]

Actually everything should be inside algoliasearch-core/src/ now, should I delete the files by hand ?

Last time it did not worked without deleting folder, but let's wait for the CI to see if it does the switch (same issue here: #386 (comment))

[shortcuts]

I was mostly wondering because we have algoliasearch-client-java-2/src already and I don't know what it's used for

[millotp]

It's not used for anything, it's empty and not commited, maybe I can remove it with the custom gen

[shortcuts]

160a4ce will delete and push correctly

[shortcuts]

Hmmm I believe there's no way for the CI to know that the whole folder has moved from / to /src... you'll maybe need to mv it manually :(

[shortcuts]

As there's no changes in the code itself, you can mv locally and push the changes, we don't have to rely on the CI here

[millotp]

No it's not correct still, the CI passed with cache but there a some files missing

[shortcuts]

N I C E!!

My comments are non blocking

[shortcuts]

Nice found!!!

Just found one question: wouldn't it be possible that this is overridden by the gen we extend?

[shortcuts]

(by that I mean: the settings we've set above)

[shortcuts]

Also, there's the JS generator that still call it in the old order

[millotp]

What I wanted to avoid was the duplication of sourceFolder and such, for js there is no duplication so no need to move it.
It's possible that the super.processOpts() overrides some value, but because the generation didn't change I assumed not.