Turned out to be something that IntelliJ did for some odd reason.
On Thu, Sep 2, 2021 at 2:26 PM Mark Bean <[email protected]> wrote: > > Just run a build of current 'main' successfully. (mvn -T 3 clean install) > > Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) > Maven home: /opt/maven/latest > Java version: 11.0.11, vendor: AdoptOpenJDK, runtime: > /opt/java/jdk-11.0.11+9 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.16.11-100.fc26.x86_64", arch: "amd64", > family: "unix" > > On Thu, Sep 2, 2021 at 2:11 PM Joe Witt <[email protected]> wrote: > > > I build on Java 11 routinely a does our GitHub CI. Im on latest maven and > > latest JDK using Azul. > > > > On Thu, Sep 2, 2021 at 10:05 AM Mike Thomsen <[email protected]> > > wrote: > > > > > The profile looks like it should be active, but when I get to the 0.11 > > > kafka processors, I get errors like this: package jakarta.xml.bind > > > does not exist > > > > > > Even manually adding -Pjigsaw to explicitly turn on those dependencies > > > doesn't work for me a full build. Any ideas? > > > > > > On Java 11 w/ Maven 3.6 IIRC. > > > > > > Thanks, > > > > > > Mike > > > > >
