I&#x27;m referring to the issue in this thread [0]. I haven&#x27;t seen any issues with how capsule (or rather, the maven caplet) does dependency resolution; it&#x27;s that you don&#x27;t have much control over transitive dependencies. This is particularly a problem when trying to create a capsule that contains the output of your internal dependencies but not your external dependencies. In other words, we&#x27;ve spent a lot of time getting gradle to package the correct set of transitive dependencies so that our code works; I have no desires to re-implement that in capsule&#x27;s limited dependency system.<p>See also this bug on maven-capsule-plugin [1]. Having tried to actually implement that strategy (albeit in gradle), it&#x27;s clear that capsule isn&#x27;t well-adapted to this sort of thing.<p>[0] <a href="https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!topic&#x2F;capsule-user&#x2F;MjtnvwtzSmI" rel="nofollow">https:&#x2F;&#x2F;groups.google.com&#x2F;forum&#x2F;#!topic&#x2F;capsule-user&#x2F;Mjtnvwt...</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;chrischristo&#x2F;capsule-maven-plugin&#x2F;issues&#x2F;28" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;chrischristo&#x2F;capsule-maven-plugin&#x2F;issues&#x2F;...</a>