Gradle plugins for building, testing and publishing .NET, Mono and Unity components and applications.
The plugins can already build, test, publish and manage dependencies of C#, Boo and UnityScript components using the Mono runtime shipped with Unity. There's also good support for consuming NuGet packages as ivy modules.
Next on the roadmap is support for using MS.NET on Windows and system Mono everywhere to ditch the Unity requirement for common usage.
Would you like to help? Join the mailing list.
- Java
- Unity 4.2 (the free version will do)
Breaking system functionality into smaller units that can be evolved and deployed independently of each other makes integration simpler because it can happen in small and localized steps. Divide and conquer.
User visible functionality is grouped and delivered as coarse grained units called bundles.
Bundles are versioned groupings of components.
Components are versioned sets of files (such as a dotnet assembly and its xml documentation file for example) stored in repositories.
Repositories are directories of components, local or remote.
Components might declare dependencies on (versions of) other components.
The version number of a component is incremented every time a new version is published in accordance with semantic versioning rules.
Components can and should be published independently of each other.
See: https://github.com/bamboo/gradle-dotnet-plugins/graphs/contributors