[java-runtime] Remove final from MonoPackageManager_Resources #2878
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In commit 75023bd we noticed an issue the
value of
MonoPackageManager_Resouces.ApiPackageNamewas""even after it was replaced at built time with a new.classfile which contained an actual value.The fix in that PR was to make the temp file in java-runtime
have a value of
nullrather than"". This made thing workbut we didn't know WHY.
After some more investigation it turns out that the value
was being inlined by the java compiler.
The code above is pointing to a string in the Constants table.
What we were expecting was that the statick method would be
called in the file generated by the build system. Making
the temp file have a
nullrather than""resulted in thefollowing code
This is why changing to
nullworked. It prevented the compilerfrom inlining the value.
This commit removes the
finalkeyword from theMonoPackageManager_Resourcesclass fields to make sure that they never get inlined.