Thanks Andi for all the work, I am interested in how it will look like afterwards :)
Maybe you can push some of the smaller/isolated changes first in separate commits so we get CI on each of those separately? On the JDK crash, I saw that elsewhere also with JDK 11! If we can make it reproducible, I can report a JDK bug via our contacts at Oracle. Thanks... Dominik. On Wed, Apr 7, 2021 at 1:53 AM Andreas Beeker <kiwiwi...@apache.org> wrote: > Hi Devs, > > I hope to commit my gradle setup by Wednesday evening. > > I haven't yet migrated all the features, but the important ones: > * JPMS / mrJar co-existing to Java 8 build > * Fixed the batik-script issue in the tests - not generally > * ooxml-lite is now created after its dependencies have been executed, so > all used schema files should be in > > Things I don't know how to fix: > * TestSignatureInfo often causing a SIGSEV when calling the XML dom api in > Java 14 (14.0.2+12-46 on Ubuntu, but works in Oracle 8) > * I've tried the fix described in > https://github.com/java9-modularity/gradle-modules-plugin/issues/97 but > to no avail, therefore I've opened (--add-exports) the junit modules. > * IntelliJ integration - it mostly works, but the syntax checker gives the > impression, that not all working constructs are understood > > Open todos: > * sonarqube calls > * refactor the gradle code duplications/mess into the root gradle - as I > was doing constant code changing iterations, I haven't dared to move it up > to the root gradle, just to find out, that the approach doesn't work with > the next to-be migrated module > * release logic > * site generation > * fix the paths in the ant build (before tomorrows commit) > * You'll see some weird duplicated dependencies, because I thought the > build order is mainly influenced by it AND I need the *-tests.jars to > execute the tests in the JPMS context. Although I've added another set of > dependsOn to the corresponding compileJava9 tasks, I don't understand how > gradles concept of using the expanded classes directories should work with > mrJars. (see https://blog.gradle.org/mrjars) > * fix the javadocs, so the HTML5 linting can be enabled > * check out JPMS plugins like > https://github.com/java9-modularity/gradle-modules-plugin or Axels plugin > (https://github.com/xzel23/JpmsGradlePlugin) > > As I have shuffled again the directories, please commit your code so I can > merge it - as I used "svn mv" this should be also ok, if you don't commit > now, but it's easier for you, if you do it before ... > > Although I've spent many many hours with gradle in the last 2 weeks and > sometimes were baffled about its reactions, I have to admit, that certain > features are slick, e.g. have a look at the ooxml-lite generation when it's > committed. > > Andi > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
