Anecdote: Print dialog popping up when running build on Java 19

[reckart]

I have recently updated the Tycho dependency in Apache UIMA from 2.x to 3.x and also recently installed a Java 19 JDK on my box. When I build UIMA now on Java, then at one point I get a popup from the printer subsystem offering my to print a PDF that contains a part of the build log. Interestingly, this does not happen if I switch JAVA_HOME to a Java 17 before starting the build.

Here is an abridged output of the build log part from that PDF covering only the parts related to Tycho:

[INFO] 28f35ad][plugin>org.eclipse.tycho:tycho-p2-repos;31morg.osgi.framework.Bundle Exceptionitory-plugin:3.0.1-2038794144] FrameworkEvent ERRORnstall) @ uimaj-eclipse-update-site --- org.osgi.framework.BundleException: : Could not resolve module: org.eclipse.tycho.embedder-api [2]
Unresolved requirement: Import-Package: org.apache.maven.execution
Could not resolve module: org.eclipse.tycho.embedder-api [2]-update-local-index) @ uimaj-eclipse-update-site ---
Unresolved requirement: Import-Package: org.apache.maven.execution
[INFO] --- maven-deploy-plugin:3.0.0:deploy (default-deploy) @ uimaj-eclipse-update-site --- [INFO] Skipping artifact deployment
atat org.eclipse.osgi.container.Module.start org.eclipse.osgi.container.Module.start (Module.java:463) (Module.java:463)rg.apache.uima:uimaj-eclipse-maven-p2-site >-------------
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run (ModuleContainer.java:1847)
at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute (EquinoxContainerAdaptor.java:136) at org.eclipse.osgi.contain er.ModuleContainer$ContainerStartLevel$2.run (ModuleContainer.java:1847)
atmat or org.eclipse.osgi.g.eclcipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.executeontainer.Modul eContainer$ContainerStartLevel.incStartLevel (ModuleContainer.java:1840)2-site/target
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel (ModuleContainer.java:1783) (EquinoxContainerAdaptor.java:136)3.0:parse-version (parse-project-version) @ uimaj-eclipse-maven-p2-site ---
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel (ModuleContainer.java:1840)
at org.eclipse.osgi.container.ModuleConta[1matdate-time (set buildYear and buildMonth) @ uimaj-eclipse-maven-p2-site --- 
....
[INFO] --- tycho-p2-repository-plugin:3.0.1:assemble-maven-repository (maven-p2-site) @ uimaj-eclipse-maven-p2-site ---
[ERROR] [1e586803-7d14-4053-86b1-a1f5d28f35ad][plugin>org.eclipse.tycho:tycho-p2-repository-plugin:3.0.1-203879414 4] org.eclipse.tycho.embedder-api
[ERROR] [1e586803-7d14-4053-86b1-a1f5
<HERE PRINTER DIALOG POPS UP AND BUILD PAUSES UNTIL DIALOG IS CLOSED>

Here is a stack trace of the seemingly responsible thread from the JVM performing the build:

"main" #1 [7939] prio=5 os_prio=31 cpu=21007.27ms elapsed=300.82s tid=0x000000013480ea00 nid=7939 waiting on condition  [0x000000016f351000]
   java.lang.Thread.State: WAITING (parking)
        at jdk.internal.misc.Unsafe.park(java.base@19.0.1/Native Method)
        - parking to wait for  <0x0000000700011b98> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
        at java.util.concurrent.locks.LockSupport.park(java.base@19.0.1/LockSupport.java:221)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@19.0.1/AbstractQueuedSynchronizer.java:715)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@19.0.1/AbstractQueuedSynchronizer.java:938)
        at java.util.concurrent.locks.ReentrantLock$Sync.lock(java.base@19.0.1/ReentrantLock.java:153)
        at java.util.concurrent.locks.ReentrantLock.lock(java.base@19.0.1/ReentrantLock.java:322)
        at jdk.internal.misc.InternalLock.lock(java.base@19.0.1/InternalLock.java:74)
        at java.io.PrintStream.write(java.base@19.0.1/PrintStream.java:787)
        at java.io.PrintStream.print(java.base@19.0.1/PrintStream.java:911)
        at org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:99)
        at org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:107)
        at org.fusesource.jansi.FilterPrintStream.print(FilterPrintStream.java:156)
        at org.fusesource.jansi.FilterPrintStream.println(FilterPrintStream.java:231)
        - locked <0x000000070000d548> (a org.fusesource.jansi.AnsiConsole$2)
        at org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:305)
        at org.eclipse.tycho.p2maven.tools.TychoFeaturesAndBundlesPublisherApplication.run(TychoFeaturesAndBundlesPublisherApplication.java:73)
        at org.eclipse.equinox.p2.publisher.AbstractPublisherApplication.run(AbstractPublisherApplication.java:279)
        at org.eclipse.tycho.plugins.p2.repository.MavenP2SiteMojo.execute(MavenP2SiteMojo.java:399)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
        at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
        at java.lang.invoke.DirectMethodHandle$Holder.invokeStatic(java.base@19.0.1/DirectMethodHandle$Holder)
        at java.lang.invoke.LambdaForm$MH/0x0000000801008800.invoke(java.base@19.0.1/LambdaForm$MH)
        at java.lang.invoke.LambdaForm$MH/0x0000000801008c00.invokeExact_MT(java.base@19.0.1/LambdaForm$MH)
        at jdk.internal.reflect.DirectMethodHandleAccessor.invokeImpl(java.base@19.0.1/DirectMethodHandleAccessor.java:156)
        at jdk.internal.reflect.DirectMethodHandleAccessor.invoke(java.base@19.0.1/DirectMethodHandleAccessor.java:104)
        at java.lang.reflect.Method.invoke(java.base@19.0.1/Method.java:578)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)

It seems to happen only in iTerm2 (I'm on a mac), but not when running in the standard Terminal.app.

When I googled for it, I found that it seems to be kind of a known issue with iTerm2 when a program sends potentially truncated control sequences to the terminal: https://gitlab.com/gnachman/iterm2/-/issues/2027

So if anybody else is puzzled by this weird behavior - now you know.

Cheers :)