I've been using ConstraintLayout of version 1.1.2 for quite some time now and it was working perfectly. Then new MotionLayout came up and I thought why not I try it out.
And everything seemed fine. So I made a mistake of using it in production. Only after a while I noticed some bug reports where ConstraintLayout was working incorrectly. But there is already some screens that depend on MotionLayout and just to remove it will require a lot of refactoring.
Can I use MotionLayout(v2.0.0-alpha-05/beta-02) and ConstraintLayout(v1.1.3) on the same project, so that screens that need MotionLayout would have v2.0.0 and screens with ConstraintLayout only would have v1.1.3? Is there some packaging tool to move MotionLayout to a different package? I tried to use shadowJar gradle plugin but failed because MotionLayout is an *.aar dependency not *.jar.
from Use MotionLayout and ConstraintLayout dependencies with different versions
No comments:
Post a Comment