Ok, there is no hope for the fix to be merged in gson, so I'd suggest we downgrade to version 2.5, which is the last one exporting those packages, and open a jirs isssue to remove the uses of the gson internal packages.
Sounds good? @gaul do you want to take care of this? Also, is there any specific desired feature that is not available in 2.5? We could go through the copy path ifn really needed. El 30 ago. 2016 4:01 p. m., "Ignasi Barrera" <ignasi.barr...@gmail.com> escribió: +1 to propose merging it to 2.6. It looks like it would be easier to get a release there. On 30 August 2016 at 16:00, Andrew Phillips <andr...@apache.org> wrote: >> Also, I don't think the exports are being added back, given the >> comments in the PR, so we should consider: > > > I just added this comment: > > https://github.com/google/gson/pull/916#issuecomment-243446866 > > @nacx: would it make sense to propose merging this into 2.6.x rather than > into master? It still leaves a breaking change in the 2.7.x releases, but > might meet with less opposition from the Gson team? > > Perhaps also worth asking in the Gson user group if there are any > recommendations how to work around/replace use of those classes? > > Regards > > ap
