Fixed
Status Update
Comments
uc...@google.com <uc...@google.com> #2
Thank you for suggesting this enhancement. We value the feedback from our community and hope to review your suggestion in an upcoming sprint.
js...@google.com <js...@google.com>
am...@gmail.com <am...@gmail.com> #4
Cant wait!
ta...@gmail.com <ta...@gmail.com> #5
This feature is really important for developers.
kr...@asmallworld.net <kr...@asmallworld.net> #6
+1
ma...@gmail.com <ma...@gmail.com> #7
+1
zh...@gmail.com <zh...@gmail.com> #8
This would be useful.
hi...@gmail.com <hi...@gmail.com> #9
+1
c....@gmail.com <c....@gmail.com> #10
Please, just STAR THE ISSUE and DON'T COMMENT +1. Every comment results in an email.
jo...@gmail.com <jo...@gmail.com> #11
+1
th...@gmail.com <th...@gmail.com> #12
I really wish the issue tracker would just auto-delete "+1" comments without sending out notifications.
jo...@gmail.com <jo...@gmail.com> #13
+100
e....@gmail.com <e....@gmail.com> #14
Dear jo..., others,
Google also decides issue priority by how many people starred a particular issue.
Everyone who starred an issue did so, because they were insterested in updates *from Google* on said issue.
Everyone who starred an issue gets an email about every comment on said issue. That, among others, includes unrelated comments and "plus ones" from undisciplined or, in your case, straight up malicious people.
I don't want to get your spam. I think I'll unstar this. I don't think I care about this issue anymore. Was that your goal? To move the star counter down and drive this issue into oblivion because everybody gets sick and tired of your behavior?
You ought to go home and rethink your life. Be a good neighbor on the Internet. Spread the message.
Thank you.
P.S. Don't reply to this message and upset 500+ PEOPLE again, like I just did.
Google also decides issue priority by how many people starred a particular issue.
Everyone who starred an issue did so, because they were insterested in updates *from Google* on said issue.
Everyone who starred an issue gets an email about every comment on said issue. That, among others, includes unrelated comments and "plus ones" from undisciplined or, in your case, straight up malicious people.
I don't want to get your spam. I think I'll unstar this. I don't think I care about this issue anymore. Was that your goal? To move the star counter down and drive this issue into oblivion because everybody gets sick and tired of your behavior?
You ought to go home and rethink your life. Be a good neighbor on the Internet. Spread the message.
Thank you.
P.S. Don't reply to this message and upset 500+ PEOPLE again, like I just did.
jr...@squareup.com <jr...@squareup.com> #15
Ok
gu...@gmail.com <gu...@gmail.com> #16
+1
sg...@google.com <sg...@google.com>
ma...@noom.com <ma...@noom.com> #17
+1
d....@infotech.team <d....@infotech.team> #18
+1
cl...@google.com <cl...@google.com>
da...@gmail.com <da...@gmail.com> #19
+65535
ke...@gmail.com <ke...@gmail.com> #20
+1
an...@gmail.com <an...@gmail.com> #21
Any update on this? this is really blocking us from using some of the java8 APIs (e.g. java.time). Though Bazel supports desugaring, its uses dx not D8.
gi...@gmail.com <gi...@gmail.com> #22
Until this is solved, you can use the Android RetroFix gradle plugin (https://github.com/SgtSilvio/android-retrofix ) to automatically backport most Java 8 APIs (java.util.function.*, Optional, CompletableFuture, java.util.stream.*) to Android APIs < 24
an...@gmail.com <an...@gmail.com> #23
Nice, thank you for letting us know about RetroFix tool, does it back port java.time? The project page API list does not contain java.time in it.
h4...@gmail.com <h4...@gmail.com> #24
Then, obviously, it doesn't…
gi...@gmail.com <gi...@gmail.com> #25
I added backporting of java.time to the RetroFix plugin with version 0.3.0.
as...@gmail.com <as...@gmail.com> #26
gu...@gmail.com <gu...@gmail.com> #27
fyi: The latest version of ProGuard 6.2.0 has support to backport java.time and the stream API to the streamsupport and ThreeTenABP libraries accordingly.
sg...@google.com <sg...@google.com> #29
Closing this as the preview is now available. Additional issues will be tracked in separate bugs.
Description