While it was done intentionally, there isn't a strong rationale for it -- I don't think there will be many (any?) cases where the packaging type will be ambiguous. I do find it strange that Gradle chooses to silently change its dependency resolution when you do this, but that's a different matter.
On Sun, Jun 8, 2014 at 9:53 PM, Jake Wharton <[email protected]> wrote: > The dependency dialog in AS apparently adds a qualifier to the > build.gradle for new dependencies (e.g., @jar). I’m basing this off > multiple reports over the last few months (I’ve never used it personally). > A side-effect of doing this is that transitive dependency resolution is > skipped which causes a headache for a lot of libraries. > > Before I file this as a bug I wanted to see whether or not this was an > explicit design decision. > > > -- > 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. > -- 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.
