Where are they getting published?

If there were put on MavenCentral or JCenter that would be a problem but it
looks like they are just on github? Someone wanting to use them has to go
find them there, and that should be a red flag anyway.


On Thu, Aug 7, 2014 at 4:41 AM, William Ferguson <
[email protected]> wrote:

> What's the Android team's stance on the non-official versions of the
> Android support libraries?
>
> Eg
> https://github.com/Prototik/HoloEverywhere/issues/842#issuecomment-49746122
>
> These libraries have the same GAV (groupId, artifactId, version) as the
> official versions but have totally different contents. This means that the
> same project built on 2 different machines can produce radically different
> outputs (unbeknownst to the developers). Or even 2 libraries both listing
> the same dependency having very different needs and producing some
> nightmare when combined (again unbeknownst to the developer doing the
> combining).
>
> These libraries are being published in the com.android.* namespace, so
> appear to be official Android team libraries which means developers are
> going to start coming to you guys for support as things start to break down
> at the edges.  If the Android team were actually publishing these artifacts
> into a public repository there wouldn't be a vacuum for incidents like this
> to occur.
>
> So what's the plan to stop this hole getting bigger and deeper?
>
> William
>
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "adt-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com

Please do not send me questions directly. Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to