[jboss-jira] [JBoss JIRA] (WFLY-13827) Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite

Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite -------------------------------------------------------------------------------------------- Key: WFLY-13827 URL: https://issues.redhat.com/browse/WFLY-13827 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 20.0.1.Final Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana Priority: Major The Galleon Layers basic integration test suite fails on IBM JDK with the following error: {noformat} [INFO] --- exec-maven-plugin:1.6.0:exec (ibmjdk.iiop.stub-creation) @ wildfly-ts-integ-basic --- error: Class javax.ejb.EJBHome not found in interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPStatefulNamingHome. error: Class javax.ejb.EJBHome not found. error: Class javax.ejb.EJBHome not found in interface org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingHome. error: Class javax.ejb.EJBHome not found. 4 errors [ERROR] Command execution failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404) at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751) at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313) 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:956) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke (Method.java:508) 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) {noformat} The reason is the ibmjdk.profile is activated independently if we are generating a slimmer server by using Galleon layers, failing in such cases.