Explore >> Select a destination
|
You are here 
|
rishigoomar.com | ||
| | | | |
ryanharter.com
|
|
| | | | | Remember the olden days of Android development? There were times when including a library in a project meant relative links to source, or using Maven. Fortunately for us, those days are long gone now with the introduction of Gradle. Gradle has made developing and consuming libraries for Android amazingly simple, and has spurred a new boom in library development for Android. We've always had a large, open, inclusive community to boast of, but over the past year or two it has only gotten better as the comm... | |
| | | | |
andreabergia.com
|
|
| | | | | In this short series, we are going to dig a bit in how one writes a gradle plugin. Our plugins won't do anything useful except some println; however I hope to manage to explain some concept and to save you some time in case you have to write one. The source code for this tutorial is available on github at https://github.com/andreabergia/sample-gradle-plugin. Our first plugin Link to heading The repository is split in two projects: gradleplugin and usage. Quite obviously, gradleplugin defines our plugin, ... | |
| | | | |
ncorti.com
|
|
| | | | | How Composite Builds can simplify your Gradle build, especially if you're building a custom Gradle Plugin. | |
| | | | |
in.relation.to
|
|
| | | Java 9 comes with a new feature very useful to library authors: multi-release JARs (JEP 238). A multi-release JAR (MR JAR) may contain multiple variants of one and the same class, each targeting a specific Java version. At runtime, the right variant of the class will be loaded automatically, depending on the Java version being used. This allows library authors to take advantage of new Java versions early on, while keeping compatibility with older versions at the same time. If for instance your library pe... | ||
