As a developer, I'd like compilation of dependencies of the app project on acornui to use classes instead of jars for rapid iteration

[fuzzyweapon]

Right now we must rely on .jar artifacts from the acornui gradle build to either publish to local maven or satisfy dependencies between acornui and app build modules when using composite builds (created and configured solely within the IDE).*

• compile issues while sweeping the current expected functionality while using composite build (created in the IDE post-gradle-importing).
• spike out composite build configuration via gradle in DSL (aka, something permanent that can be turned on with a property, if acceptable)
• compile issues with gradle generated composite build option
• Pitch to @nbilyk best way to go
• generate tickets for implementation (link back to this)

*This is slow in general and can easily lead the dev to experience crazy amounts of slowdown in the gradle-runner compile time if they goof up and alternate how they build the library (not confirmed but it's somewhere within this user scenario). Given build and rebuild project in the app IDE project triggers an IDE build of both acornui and the app project, this is not great. In composite, there are a bunch of rough edges that make IDE building with it perilous.

[fuzzyweapon]

Note: If a project uses some dependency rules to automatically provide a common version, the IDE will not do any dependency substitution at all and treats all dependencies as external.

[fuzzyweapon]

Superseded by #157, closing