Expose an additional jar that doesn't include OSGi manifest information

Danny Weinberg · Kannan Goundan · commit 466f66a7ad1d · 2016-09-30T14:34:02.000-07:00
Currently doing a noop build of the SDK jar takes quite a while (for me, the
jar task itself takes about 2.5 seconds to determine that it's up to date). I
dug into this and it turns out that this is due to an inefficiency in the OSGi
plugin when determining if the OSGi manifest is up to date.

On my machine, a noop jarWithoutOsgi task is ~50x faster, taking about 0.05
seconds.
diff --git a/build.gradle b/build.gradle
@@ -1,4 +1,4 @@
-import org.gradle.internal.os.OperatingSystem;
+import org.gradle.internal.os.OperatingSystem
 
 apply plugin: 'java'
 apply plugin: 'osgi'
@@ -93,6 +93,10 @@ dependencies {
     testCompile 'com.google.guava:guava:19.0'
 }
 
+configurations {
+    withoutOsgi.extendsFrom compile
+}
+
 processResources {
     filesMatching('**/sdk-version.txt') {
         expand project.properties
@@ -216,6 +220,11 @@ jar {
     }
 }
 
+task jarWithoutOsgi(type: Jar, dependsOn: classes) {
+    classifier 'withoutOsgi'
+    from sourceSets.main.output
+}
+
 task sourcesJar(type: Jar, dependsOn: classes) {
     classifier = 'sources'
     from sourceSets.main.allSource
@@ -229,6 +238,7 @@ task javadocJar(type: Jar, dependsOn: javadoc) {
 artifacts {
     archives sourcesJar
     archives javadocJar
+    withoutOsgi jarWithoutOsgi
 }
 
 install {
