|Re: [cbi-dev] Signing service configuration|
Only in cases I need to do so. We have 3 runtime libraries that could be used in an android app.
I’m not very familiar with android packaging, but I recall that META-INF/MANIFEST.MF is the only
exception of the "duplicate resource“ constraint. I found a maven apk packaging plugin that has an option to ignore duplicates, this seems not be possible using gradle or in AndroidStudio.
Yes, I also think apk packager should handle this. I’m not an android developer, so I’m not sure what’s the right solution.
We have only the 3 library jars that we produce and that could/should be used in android: o.e.xtend.lib, o.e.xtend.macro.lib and o.e.xbase.lib. If someone needs other 3rd party libs, e.g. guava, they will fetch them from the maven central, so orbit is out of scope.
That is up to users to decide what to do with the resulting apk file. I think there should be a signing service for the android apps.
Thanks for your reply and best regards,
Description: Message signed with OpenPGP using GPGMail