-
Notifications
You must be signed in to change notification settings - Fork 362
The @packaging is ignored by the Android resolver #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
AFAIK the only place I messed with the packaging was to fallback to srcaar when "aar" is specified as the packaging. |
I did some tests and it seems fff89b8#diff-c0119d524241ce57b8198e4bb14da162 introduced a behavior change. Requesting a non-existing
Requesting without the packaging with 858ade1 works (as expected):
Requesting a non-existing
Requesting without the packaging with fff89b8 works (as expected):
It seems to me like the
|
Uh oh!
There was an error while loading. Please reload this page.
Hi,
In some cases I want to specify the packaging (like
@jar
) in order to skip the POM file processing. This may be because I don't want its dependencies to be automatically downloaded, or because the POM file is just invalid.While looking at older issues (like this: #128) it seems like at some point the process failed to download a package if the specified packaging didn't exist (which makes sense to me). Now it seems to always download the POM file, ignoring the specified packaging, and then it downloads the packaging specified in the POM (and it processes all the dependencies).
Trying to replicate the issue from #128 I get this result:
I would expect this to fail because I specified
@jar
and the jar file doesn't exist for this package, but it downloads the.aar
file instead. Is this an expected behavior? Is there a way to make it behave as I expected? (like in the old releases)Thanks!
The text was updated successfully, but these errors were encountered: