Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).
Build: #652 was successful Changes by Florian Schmaus <flo@geekplace.eu>
Code commits
Smack (master)
-
Florian Schmaus <flo@geekplace.eu> effe82a9c98625d64e5155b17b672aecf07cec12
Merge pull request #346 from vanitasvitae/fixAndroid
Don't compile android.jar contents into smack-android jar -
Paul Schaub <vanitasvitae@fsfe.org> 4ed4e8f71ca2c1a74751dd87e9b911fe597b7fa8 m
Don't compile android.jar contents into smack-android jar
gradles compile command (which is deprecated and should be replaced with implementation) includes the arguments resources into the result jar.
That means that smack-android will contain resources found at the android boot classpath.
This results in a +~11mb increase in size of the resulting apk when including Smack as a composite build. The increase comes from 11mb of Android resources, mainly drawables.
compileOnly (formerly provided) on the other hand will assert that the android.jar classes are provided by the system, which is probably what we want in this case.