For the records, the very same frustration was my initial driver to start working on log4j2-logstash-layout as a separate project. (That said, this path led other advantages for the plugin.) I think this awkwardly high entry barrier repels many potential contributors. Sometimes you just want to fix a one liner, but end up throwing the towel once you figure out the project does not even build properly in your IDE. Just my 2 cents...
On Sat, Jun 8, 2019 at 10:33 PM Matt Sicker <[email protected]> wrote: > The maven config has gotten so complicated now that IntelliJ no longer > knows how to compile anything or run tests. I've tried using Java 8 as > a default JDK, but that leads to errors because IntelliJ doesn't > recognize the java9 modules as using a different JDK. I tried manually > changing those modules, but then I get some javac error with no error > message. > > Next, I tried using Java 12 as the default JDK, but then came across > an issue in a test that I fixed in master. Now I'm stuck trying to get > the log4j-jmx-gui module to compile in Java 12 because jconsole.jar is > now jdk.jconsole.jmod, and I can't find any docs on using maven to > generate any JPMS stuff. > > To be clear, this all builds perfectly fine from the command line > using maven directly. > > -- > Matt Sicker <[email protected]> >
