Closed GoogleCodeExporter closed 8 years ago
Just renaming the package shouldn't cause an issue, but there's not enough
information in this bug to cause the issue you reported. Also, it should not be
necessary to rename the package.
Original comment by nonot...@gmail.com
on 18 Feb 2013 at 8:15
Original issue reported on code.google.com by
tycjone...@gmail.com
on 24 May 2012 at 12:18