Closed GoogleCodeExporter closed 9 years ago
We actually used to have this, because we used to have a need for it. But it's
unclear what purpose it would serve today. Guava generally doesn't provide
things that lack sufficiently compelling functionality even when they would
prevent multiple projects from defining their own copies.
Original comment by kevinb@google.com
on 10 Feb 2014 at 5:10
I see. I do think there is a need for a project that model at the meta-level
the distinct Java artifacts, such as the reference types mentioned above.
But as you say, that is (maybe?) outside the current Guava scope.
Thanks for the clarification.
Original comment by sergio...@gmail.com
on 11 Feb 2014 at 2:43
This issue has been migrated to GitHub.
It can be found at https://github.com/google/guava/issues/<issue id>
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:10
Original comment by cgdecker@google.com
on 3 Nov 2014 at 9:07
Original issue reported on code.google.com by
sergio...@gmail.com
on 9 Feb 2014 at 11:00