Upgrading to 4.12 to avoid bug about proguard

[rowillia]

Upstream is taking these fixes into 5.0!

I can move this up to 4.12 next week, AFK for the American holiday weekend.
On May 23, 2014 1:30 AM, "Paul Blundell" [email protected] wrote:

How come you forked at 4.11 and is their a possibility of moving to 4.12
or 5.0?

I ask because of a serious bug with Proguard & Android (when using Google
Play Services) that affects 4.11 & is fixed in 4.12.

http://sourceforge.net/p/proguard/bugs/505/

In any androi dproject with the 'Google Play Service' library to use AdMob
or any other,
Proguard 4.11 spit out below error. 4.10 is ok with same proguard script.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3
.

[rowillia]

@blundell It looks like Eric hasn't released the source code to 4.12 yet, so I can't upgrade past it.

[blundell]

You're right it is not here http://sourceforge.net/p/proguard/code/ci/default/tree/

I've attempted to get an answer from Eric here of if there is a possible release date https://sourceforge.net/p/proguard/discussion/182456/thread/84c6ace6/

[tonyxiao]

5.0beta code is out, a good time to update?

[rowillia]

@tonyxiao Awesome! Thanks, I'll take a look.

[charlesmunger]

I can do the 4.11 -> 5.0 upgrade. Is it OK to do it as one big patch, or do you want me to attempt to preserve proguard's history?

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[alsutton]

We've now moved to 5.2.1, so I'm closing the issue. Thanks for reporting it.