Closed ataulm closed 10 years ago
Sorry about that. Just updated documentation. To resolve dependencies you have to add our repository to your project. Please add following to your build.gradle:
repositories {
maven {
url 'https://raw.githubusercontent.com/onepf/OPF-mvn-repo/master/'
}
}
Does this mean that the open-iab aar is being fetched from that repo, or there are dependencies inside open-iab which are found in that repo?
I don't follow how this worked to solve the no class def issue; in any case I would have expected the resources imported via compile 'org.onepf:openiab:0.9.8'
to pull in all the dependencies required - it feels obtuse to have another requirement to add a third-party maven repo (unless that's where the openiab library lives).
or there are dependencies inside open-iab which are found in that repo?
Yes, dependencies are to blame..
I would have expected the resources imported via compile 'org.onepf:openiab:0.9.8' to pull in all the dependencies required.
I get your point. Unfortunately there's not a lot of ways we can go about it:
repository
tag in pom filled from gradle maven plugin. But it doesn't seem to work. I wasn't even able to find documentation about this feature.So... yeah. We'll probably stay at current point for a little while and see how it goes. If you have other ideas I'd be grad to here them out.
na fair enough - we've had similar issues before. Thanks for explaining.
You're welcome.
Has the usage of the library changed since the last version? In 0.9.8 (I tried this using the
compile 'org.onepf:openiab:0.9.8'
and also building theaar
from master myself), I get an error:Looking in
master
this class is still present, and public. Has the building of the library changed since version at commit c3ff201a585de5b6db3e99727eb523ea75f222ec in such a way as to effect this error?