Modules, Jigsaw, Layers

[nsoft]

This ticket is for discussion of what features should be added in consideration of the java 9+ Jigsaw related features. Here's a relevant slide share, but it's not entirely clear if this is exactly what's in Java 9, or if it's discussing some earlier stage of Jigsaw...

https://www.slideshare.net/nikitalipsky94/escaping-the-jar-hell-with-jigsaw-layers-gee-con

[nsoft]

My current thinking is that this is going to be a good way to isolate conflicting versions. What I'd like to achieve is something like this:

unojar {
  unoJar "build/testJar2.jar"                        // <<< (1)
  manifestAttrs ("Test-Attribute" : "TestValue")     // <<< (2)
  appMainClass "com.needhamsoftware.unojar.TestMain" // <<< (3)
  appFiles {                                         // <<< (4)
    fileset(dir: 'build/classes/java/test') {
      include(name: '**/TestMain.class')
    }
  }
  depLibs {                                          // <<< (5)
    fileset(dir: 'build/libs') {
      include(name: 'libtest.jar')
    }
  }
  moduleLayer {
    layerName 'tikaDeps'
    configuration.tikaLibs
  }
}

which will create a module layer below the default layer and provide it with it's own jar classpath that loads from /tikaDeps/ inside the uno-jar rather than /libs