There shouldn’t be anything circular. If there was Maven should have caught it. Java9 needs to build first and then log4j-api unzips java9 and includes it into its jar. The only issue might be that there are classes with that have the same package and name in the two modules. But that is just how multi-release jars work.
Ralph > On Jun 19, 2017, at 8:00 PM, Gary Gregory <[email protected]> wrote: > > Hi, > > FWIW, the current set up in Git puts Eclipse in some sort of workspace > building look. It can kill whatever it is going and keep editing and > running code. But it does get caught in the loop again. Is there anything > circular in the set up for Java 9? > > Gary > > On Sun, Jun 18, 2017 at 11:42 PM, Ralph Goers <[email protected]> > wrote: > >> To tell you would have to look at the zip file. If it contains >> /classes/META-INF/versions/9 you should be fine. To be sure look at the >> log4j-api jar. It should contain META-INF/versions/9/org/ >> apache/logging/log4j/util/StackLocator.class >> >> Ralph >> >>> On Jun 18, 2017, at 10:23 PM, Gary Gregory <[email protected]> >> wrote: >>> >>> When I build (with Java 8) I now see: >>> >>> [INFO] --- maven-assembly-plugin:3.0.0:single (zip) @ log4j-api-java9 >> --- >>> [INFO] Reading assembly descriptor: src/assembly/java9.xml >>> *[ERROR] OS=Windows and the assembly descriptor contains a *nix-specific >>> root-relative-reference (starting with slash) >> /classes/META-INF/versions/9* >>> [INFO] Building zip: >>> C:\vcs\git\apache\logging\logging-log4j2\log4j-api- >> java9\target\log4j-api-java9-2.8.3-SNAPSHOT.zip >>> [INFO] >>> >>> and the build continues seemingly OK. >>> >>> Not sure how bad that is. >>> >>> Gary >> >> >>
