anything happen to com.google.android.gms:google-play-services lately

[spyhunter99]

I went to build today and found that the following artifact can no longer be resolved...

<groupId>com.google.android.gms</groupId>
<artifactId>google-play-services</artifactId>
<type>apklib</type>
<version>25.0.0</version>

after updating with the SDK manager and redeploying with this tool, i find that the artifact doesn't appear to exist anymore. Not sure what the replacement is or if my rig is broken

[mosabua]

Yeah... I wiped by SDK and reinstalled and lots of stuff is broken ... another fun update. Pull requests to fix things up are welcome..

[spyhunter99]

bummer

On Mon, May 30, 2016 at 11:25 AM, Manfred Moser notifications@github.com
wrote:

Yeah... I wiped by SDK and reinstalled and lots of stuff is broken ...
another fun update. Pull requests to fix things up are welcome..

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#295 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AB4kGaOuG2eVgQwz1CITQpLIEyf_JuhEks5qGwGFgaJpZM4IpaEb
.

[mosabua]

Well.. I got the CI build green at least so it should be usable again for the core use cases like android.jar of various versions plus the repositories. I will work on add ons and extras soon..

[mosabua]

Play services is completely different now. Not sure where to get the apk from now to be honest. You would have to have an internal repo with the old artifact from a prior version deployed. If you need that I can see if I can find it on an old server.

[spyhunter99]

i love the fact that they just delete the old stuff. isn't the point of version'd artifacts is to be able to roll back?

[malachid]

They don't use repos correctly. They rename, delete, etc. If you tag a
build that depends on google repos, a year later, it is unlikely that it
can be repeated.
On Jun 3, 2016 5:45 PM, "spyhunter99" notifications@github.com wrote:

i love the fact that they just delete the old stuff. isn't the point of
version'd artifacts is to be able to roll back?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#295 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAYLpa2625qYKuZSN4k4XmDqHc4UQscYks5qIMq0gaJpZM4IpaEb
.

[mosabua]

Contact me via email .. I might have some of the needed artifacts..

[spyhunter99]

@mosabua any solutions? we've been broke for a while...and I can't even count how many man hours have been spent trying to get gradle to actually perform a release to central.

[spyhunter99]

looks like they removed the pom.xml from the jar...at least i think that's the case. the source is still there

[spyhunter99]

can we just make our own pom and carry on?

[Mohsenrezayii]

I went to build today and found that the following artifact can no longer be resolved...

<groupId>com.google.android.gms</groupId>
<artifactId>google-play-services</artifactId>
<type>apklib</type>
<version>25.0.0</version>

after updating with the SDK manager and redeploying with this tool, i find that the artifact doesn't appear to exist anymore. Not sure what the replacement is or if my rig is broken