-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ResourceClassGenerator always generates final fields #756
Comments
Tried updating to the newer 2.2.3 but I don't know how to fix ManifestMergerMojo, since that class seems to heavily depend on classes which are gone in 2.2.3 |
I can help you with that class. Do you have a branch with the ongoing changes? |
Not yet, my "fix" was to always call the SymbolWriter in a way that does not use final fields, but that would be wrong. I'm not sure how I can detect if the generation is run during test lifecycle (and inside an aar library). |
Pushed my minimal changes: https://github.com/sprylab/android-maven-plugin/tree/final_ids |
I've created a WIP PR: #757 |
Hi guys. I've noticed that you are currently working on PR:#757 Thanks |
You can build it locally and try it out. It would be good to know how it works for your use cases |
Fixed with #757 |
It seems that the old version of SymbolWriter from the android builder always writes the fields as final fields.
Updated to 2.2.3 the SymbolWriter class allows to specify whether to use
final
fields.This should probably be fixed for aar libraries as their tests currently fail with robolectric 3.2.1 (see robolectric/robolectric#2847)
The text was updated successfully, but these errors were encountered: