hi,
It is possible to know the arborescence tree of a project. and all the solution we tried before finding the rigth gradle, JRE and NDK for one android platform.
How information tree are designed ?
To me at least it is totally unclear what you are asking.
Mind elaborating a bit on what you mean and want to know?
yes i will try.
that it is like i imagine a project could be organized in gradle.
- Project
* android studio version
* JRE(java)
* gradle version
* build gradle version
* android verion
* NDK version
* File version
So my question is how gradle organize the information structure of a project. So when it build the project is looking first to the name, the JRE,theGradle exct. What is the order of searching information to buid or rebuild.
I ask that because i had big trouble using 2 IDE version and testing different NDK. At th end i had to clean everythings, IDE and .gradle. Let said that after 8 years it is not a bad idea. 
Are you asking the same thing as in your other thread?
I already said there, that there is no such structure.
Or did you mean to suggest doing it like that?
Then this is the wrong place, this is a community forum where users like me helping users like you.
You would need to post a feature request on GitHub Gradle project.
But to be honest I would not expect it to be accepted, but I might as well be wrong. 
No, i just ask how gradle organize the information.
I just give an example how i would do it. It is just to explain the form of the response.
Thanks,
It is not up to date with what i see in my .gradle directory.
But this does not explain how information are stored.
Example : i build with NDK A and then NDK B. the build will be donne for the to version of NDK. So i have in fact 2 tree of my project. But i could also build with Cmake or android.nk. It is again 2 version of the project. So at the end i got 4 tree information concerning my project. And if i force the logic, if i build for 2 SDK version, i got two phonne to test. Arborecsence of the project information increase. I think it is what append to me those days.
By the way i make it work again. But the android.mk wich is used, i think during prebuild, is strange with the new gradle version. Compiling source code to library has completly changed between 4.1 cabary and 2022 Android Studio Chipmunk.
It is not up to date with what i see in my .gradle directory.
Why not? What do you see? For me the information is up-to-date as far as I can tell.
Sorry, but I think I still do not get your question right.
Which information are you talking about and where is it stored?
But the android.mk wich is used, i think during prebuild, is strange with the new gradle version. Compiling source code to library has completly changed between 4.1 cabary and 2022 Android Studio Chipmunk.
This probably does not have much to do with Gradle though, but maybe with the Android Gradle Plugin and how it does things which is always “special”, or maybe with Android Studio that does special things which then would be even less a Gradle topic. 
Yes i agree it is not Gradle problem. I think gradle is a framework that can be changed by the user. So android can had everything he want inside do allow or refuse thing to be donne depending on the gradle version we must used with the android studio version. So the all processus of build can change all the time.
What about the parser. can android change it to add command or it is gradle only gradle staff.
Example from android studio 3.1 and 4.1 the dependency call where changed from “compile” to "implementation ".
I think it is important to user to anderstand who does what.
Thanks again for patience, help and knoledge sharing.
compile and implementation are configurations coming from the java plugin.
compile was deprecated many many years and finally was removed in Gradle 7.0.
Semantically, both are more or less the same to great lengths.
AGP cannot “change the parser” in the literal sense.
It can though register extensions, configurations, and so on, which then defines what is valid syntax or not in a build script.
So android user can mofified it as he want.
Theoretically yes, practically that does not make much sense.
Sorry, the question i ask is not what i wanted to said.
So android can modified the configuration as they want. Change or add control on some part of the build. That is why there are so many build version. One version can do something that next version cannot. Control java code or library acces and so on.
Android can have complete hand on the configuration of gradle for there IDE. Eclipse could do something else.
The Android Gradle Plugin defines how it works in the Android ecosystem. Android Studio and Eclipse have to adapt to that to property support Android builds. Which IDE you use should never influence your build scripts, except maybe if you have auxiliary IDE-specific things like the idea-ext plugin.
hi,
Yes i start to anderstand that gradle specify the work that must be done to build android project into AKP. That is clear for me know. Gradle is a frameWork to build project and to get get and store dependencies. But they do not store anythings about the project, i cannot find anything concerning project in .gradle folder,or i did not find it.
Gradle is the robot how build the AKP but not the provider of the input information and nethier the one how store the resulted information. It look like éverthings are stored in “user/user/appdata/Local/google” and “user/user/appdata/Roaming/google” folders.