August 2020 - jboss-jira - Jboss List Archives

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

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13791: ------------------------------------------- Summary: Manual IIOP/CORBA stub generation fails on IBM JDK when running the Galleon Layers testsuite Key: WFLY-13791 URL: https://issues.redhat.com/browse/WFLY-13791 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 20.0.1.Final Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana 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. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-324) Bootable JAR - Add an alternative way to the CLI in order to configure the server

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFWIP-324?page=com.atlassian.jira.plugin... ] Fabio Burzigotti commented on WFWIP-324: ---------------------------------------- Thanks [~jdenise] - as agreed let's make sure to turn this into a valid WFLY enhancement issue for future development. > Bootable JAR - Add an alternative way to the CLI in order to configure the server > --------------------------------------------------------------------------------- > > Key: WFWIP-324 > URL: https://issues.redhat.com/browse/WFWIP-324 > Project: WildFly WIP > Issue Type: Enhancement > Reporter: Fabio Burzigotti > Assignee: Jean Francois Denise > Priority: Major > > Using the CLI to configure the packaged server seems not to be the optimal or final solution, since it reveals implementation details about the runtime and its usage is not immediate. > Furthermore that configuration makes POM definition more cumbersome IMHO. > This WFWIP is to discuss an enhancement as an alternative to the CLI scripts for a static configuration of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1181) DropDown - Check open and close states first - optimize

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1181?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1181. ----------------------------------- Resolution: Done > DropDown - Check open and close states first - optimize > ------------------------------------------------------- > > Key: SWSQE-1181 > URL: https://issues.redhat.com/browse/SWSQE-1181 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-324) Bootable JAR - Add an alternative way to the CLI in order to configure the server

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-324?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFWIP-324: -------------------------------------------- [~fburzigo] I agree that we have a gap there. Layers abstract the configuration, CLI brings you back to require a detailed knowledge of its content. CLI is, for now, the only supported/well known way to apply changes to a configuration. Introducing a new way seems outside the scope of XP 2.0. > Bootable JAR - Add an alternative way to the CLI in order to configure the server > --------------------------------------------------------------------------------- > > Key: WFWIP-324 > URL: https://issues.redhat.com/browse/WFWIP-324 > Project: WildFly WIP > Issue Type: Enhancement > Reporter: Fabio Burzigotti > Assignee: Jean Francois Denise > Priority: Major > > Using the CLI to configure the packaged server seems not to be the optimal or final solution, since it reveals implementation details about the runtime and its usage is not immediate. > Furthermore that configuration makes POM definition more cumbersome IMHO. > This WFWIP is to discuss an enhancement as an alternative to the CLI scripts for a static configuration of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-325) Bootable JAR - Provide a way for creating bootable JAR from Java API

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-325?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFWIP-325: -------------------------------------------- [~fburzigo] that is something that could be achieved, we did something similar for Galleon CLI: [https://github.com/wildfly/galleon/tree/master/cli] Not a small task, I would postpone it after XP 2.0. > Bootable JAR - Provide a way for creating bootable JAR from Java API > -------------------------------------------------------------------- > > Key: WFWIP-325 > URL: https://issues.redhat.com/browse/WFWIP-325 > Project: WildFly WIP > Issue Type: Enhancement > Reporter: Fabio Burzigotti > Assignee: Jean Francois Denise > Priority: Major > > This is to propose for an enhancement in order to have an API to access the {{wildfly-jar-maven-plugin}} business logic, as it could be really useful for contexts like testing on OCP and automation development. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-330) Bootable JAR - Cloud - No HA support in default configuration.

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFWIP-330?page=com.atlassian.jira.plugin... ] Jean Francois Denise updated WFWIP-330: --------------------------------------- Description: When no Galleon Layers are provisioned, the default configuration standalone-microprofile.xml is used. For cloud, having an HA configuration makes more sense. The Bootable JAR maven plugin should provision a standalone-microprofile-ha.xml NB: HA features are enabled for WildFly/EAP/XP S2I builder image default configurations. was: When no Galleon Layers are provisioned, the default configuration standalone-microprofile.xml is used. For cloud, having an HA configuration makes more sense. The Bootable JAR maven plugin should provision a standalone-microprofile-ha.xml NB: HA features are enabled for EAP/XP S2I builder image default configurations. > Bootable JAR - Cloud - No HA support in default configuration. > -------------------------------------------------------------- > > Key: WFWIP-330 > URL: https://issues.redhat.com/browse/WFWIP-330 > Project: WildFly WIP > Issue Type: Bug > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > > When no Galleon Layers are provisioned, the default configuration standalone-microprofile.xml is used. For cloud, having an HA configuration makes more sense. > The Bootable JAR maven plugin should provision a standalone-microprofile-ha.xml > NB: HA features are enabled for WildFly/EAP/XP S2I builder image default configurations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7419) Include RESTEasy WADL module

by Weinan Li (Jira)

[ https://issues.redhat.com/browse/WFLY-7419?page=com.atlassian.jira.plugin... ] Weinan Li commented on WFLY-7419: --------------------------------- I'll start work on the example and doc. > Include RESTEasy WADL module > ---------------------------- > > Key: WFLY-7419 > URL: https://issues.redhat.com/browse/WFLY-7419 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Frank Langelage > Assignee: Yogesh Vedpathak > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5100) Add missing distribution repo tags in core-feature-pack-common-licenses.xml

by Roberto Oliveira (Jira)

Roberto Oliveira created WFCORE-5100: ---------------------------------------- Summary: Add missing distribution repo tags in core-feature-pack-common-licenses.xml Key: WFCORE-5100 URL: https://issues.redhat.com/browse/WFCORE-5100 Project: WildFly Core Issue Type: Task Reporter: Roberto Oliveira Assignee: Roberto Oliveira Both org.apache.sshd:sshd-common and org.apache.sshd:sshd-core are missing distribution tag in licenses file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12616) Vulnerability in version wildfly-jdr-16.0.0.Final: CVE-2017-7503

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12616?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12616: ------------------------------------ Security: (was: Security Issue) > Vulnerability in version wildfly-jdr-16.0.0.Final: CVE-2017-7503 > ---------------------------------------------------------------- > > Key: WFLY-12616 > URL: https://issues.redhat.com/browse/WFLY-12616 > Project: WildFly > Issue Type: Bug > Reporter: Rory Torney > Assignee: Brian Stansberry > Priority: Major > Fix For: 14.0.0.Final > > > During a security scan the following vulnerability was raised against wildfly-jdr-16.0.0.Final (I'm not sure if this issue is also present in 17.0.1.Final): > https://nvd.nist.gov/vuln/detail/CVE-2017-7503 > According to this: > https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... > upgrading JBoss EAP to a version >= 7.2 should resolve this, though I'm not entirely sure how EAP versions map to wildfly versions? According to the StackOverflow post below, the version of wildfly in which this issue was raised (16.0.0.Final) , should be mapped to EAP >= 7.2, but since this issue is being reported, maybe that is not the case: > https://stackoverflow.com/questions/53448832/what-version-of-wildfly-corr... > Bug reports: > https://access.redhat.com/security/cve/cve-2017-7503 > https://bugzilla.redhat.com/show_bug.cgi?id=1451960 > https://bugzilla.redhat.com/show_bug.cgi?id=1451961 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-330) Bootable JAR - Cloud - No HA support in default configuration.

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-330: ------------------------------------------ Summary: Bootable JAR - Cloud - No HA support in default configuration. Key: WFWIP-330 URL: https://issues.redhat.com/browse/WFWIP-330 Project: WildFly WIP Issue Type: Bug Reporter: Jean Francois Denise Assignee: Jean Francois Denise When no Galleon Layers are provisioned, the default configuration standalone-microprofile.xml is used. For cloud, having an HA configuration makes more sense. The Bootable JAR maven plugin should provision a standalone-microprofile-ha.xml NB: HA features are enabled for EAP/XP S2I builder image default configurations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020