Android Studio 3.2 Generated java
up vote
7
down vote
favorite
I just updated android studio in latest version and here is a new directory named Generated Java, can anyone explain what is it and any effect on projects if I delete this directory from root directory of project.
Please let me know if you know anything about it.
Thanks
android 
android-studio asked Sep 28 at 5:34
Sandeep Parish
1,0001113
add a comment |
up vote
7
down vote
favorite
I just updated android studio in latest version and here is a new directory named Generated Java, can anyone explain what is it and any effect on projects if I delete this directory from root directory of project.
Please let me know if you know anything about it.
Thanks
android android-studio asked Sep 28 at 5:34
Sandeep Parish
1,0001113
add a comment |
up vote
7
down vote
favorite
up vote
7
down vote
favorite
I just updated android studio in latest version and here is a new directory named Generated Java, can anyone explain what is it and any effect on projects if I delete this directory from root directory of project.
Please let me know if you know anything about it.
Thanks
android android-studio asked Sep 28 at 5:34
Sandeep Parish
1,0001113
I just updated android studio in latest version and here is a new directory named Generated Java, can anyone explain what is it and any effect on projects if I delete this directory from root directory of project.
Please let me know if you know anything about it.
Thanks
android android-studio android android-studio asked Sep 28 at 5:34
Sandeep Parish
1,0001113
asked Sep 28 at 5:34
Sandeep Parish
1,0001113
edited Nov 19 at 7:12
asked Sep 28 at 5:34
Sandeep Parish
1,0001113
asked Sep 28 at 5:34
Sandeep Parish
1,0001113
asked Sep 28 at 5:34
Sandeep Parish
1,0001113
1,0001113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
10
down vote
This folder has already been in your project, only now it is highlighted in the Android view mode of the project explorer. Its location is actually build/generated/source/r/<current flavor>/<current build type>/.
The classes you can find here are all the classes the project will be built from, including the libraries.
Inspecting these could be useful when you are having issues with generated code, such as annotation processors. For example, the databinding library, ButterKnife, or Dagger 2 all generate java classes based on your annotations, which you can see in this directory.
If you delete the directory, it will make the next build slower, because it needs to regenerate these files again, instead of reusing them.
Which means they will reappear anyways, so there's no point in doing that.
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
10
down vote
This folder has already been in your project, only now it is highlighted in the Android view mode of the project explorer. Its location is actually build/generated/source/r/<current flavor>/<current build type>/.
The classes you can find here are all the classes the project will be built from, including the libraries.
Inspecting these could be useful when you are having issues with generated code, such as annotation processors. For example, the databinding library, ButterKnife, or Dagger 2 all generate java classes based on your annotations, which you can see in this directory.
If you delete the directory, it will make the next build slower, because it needs to regenerate these files again, instead of reusing them.
Which means they will reappear anyways, so there's no point in doing that.
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
add a comment |
up vote
10
down vote
This folder has already been in your project, only now it is highlighted in the Android view mode of the project explorer. Its location is actually build/generated/source/r/<current flavor>/<current build type>/.
The classes you can find here are all the classes the project will be built from, including the libraries.
Inspecting these could be useful when you are having issues with generated code, such as annotation processors. For example, the databinding library, ButterKnife, or Dagger 2 all generate java classes based on your annotations, which you can see in this directory.
If you delete the directory, it will make the next build slower, because it needs to regenerate these files again, instead of reusing them.
Which means they will reappear anyways, so there's no point in doing that.
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
add a comment |
up vote
10
down vote
up vote
10
down vote
This folder has already been in your project, only now it is highlighted in the Android view mode of the project explorer. Its location is actually build/generated/source/r/<current flavor>/<current build type>/.
The classes you can find here are all the classes the project will be built from, including the libraries.
Inspecting these could be useful when you are having issues with generated code, such as annotation processors. For example, the databinding library, ButterKnife, or Dagger 2 all generate java classes based on your annotations, which you can see in this directory.
If you delete the directory, it will make the next build slower, because it needs to regenerate these files again, instead of reusing them.
Which means they will reappear anyways, so there's no point in doing that.
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
This folder has already been in your project, only now it is highlighted in the Android view mode of the project explorer. Its location is actually build/generated/source/r/<current flavor>/<current build type>/.
The classes you can find here are all the classes the project will be built from, including the libraries.
Inspecting these could be useful when you are having issues with generated code, such as annotation processors. For example, the databinding library, ButterKnife, or Dagger 2 all generate java classes based on your annotations, which you can see in this directory.
If you delete the directory, it will make the next build slower, because it needs to regenerate these files again, instead of reusing them.
Which means they will reappear anyways, so there's no point in doing that.
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
edited Oct 29 at 6:52
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
answered Sep 28 at 5:53
Daniel Zolnai
9,35533859
9,35533859
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52548924%2fandroid-studio-3-2-generated-java%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
