April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-11918: ------------------------------ Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > Fix For: 17.0.0.Beta1 > > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-11918. ------------------------------- Resolution: Done > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > Fix For: 17.0.0.Beta1 > > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] Kabir Khan reopened WFLY-11918: ------------------------------- > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > Fix For: 17.0.0.Beta1 > > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-11918: ----------------------------------- [~yersan] I am reopening this as I have merged the revert > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > Fix For: 17.0.0.Beta1 > > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-674) Identify produckey and product line for Istio

by Tiago Moreira Vieira (Jira)

[ https://issues.jboss.org/browse/SWSQE-674?page=com.atlassian.jira.plugin.... ] Tiago Moreira Vieira commented on SWSQE-674: -------------------------------------------- [~pyadav] Does this link help? [https://pp.engineering.redhat.com/pp/product/smm/overview] > Identify produckey and product line for Istio > --------------------------------------------- > > Key: SWSQE-674 > URL: https://issues.jboss.org/browse/SWSQE-674 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Tiago Moreira Vieira > Priority: Major > Labels: pqi > > the produckey for Istio > also which product line its map to? what is product hierarchy for these two products? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11929) Update Hibernate ORM to 5.4.2

by Андрей Григорьев (Jira)

Андрей Григорьев created WFLY-11929: --------------------------------------- Summary: Update Hibernate ORM to 5.4.2 Key: WFLY-11929 URL: https://issues.jboss.org/browse/WFLY-11929 Project: WildFly Issue Type: Component Upgrade Affects Versions: 16.0.0.Final Reporter: Андрей Григорьев Assignee: Brian Stansberry Fix For: 17.0.0.Beta1 Please update hibernate orm to 5.4.x version, because version 5.3.x have significant bug: https://hibernate.atlassian.net/browse/HHH-12436 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-14) When using the combination of drools-guvnor and jBPM-designer on JBoss in IE 9 new diagrams are not loaded after creation

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-14?page=com.atlassian.jira.plugin.... ] Jozef Marko closed DROOLS-14. ----------------------------- Resolution: Done Closing due to dropped IE support. > When using the combination of drools-guvnor and jBPM-designer on JBoss in IE 9 new diagrams are not loaded after creation > ------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-14 > URL: https://issues.jboss.org/browse/DROOLS-14 > Project: Drools > Issue Type: Bug > Environment: Windows 7, IE9, JBoss AS 7.1.1.Final, jBPM Designer 2.4.0.Final, Drools Guvnor 5.5.0.Final > Reporter: Nils Miehe > Assignee: Mark Proctor > Priority: Major > Labels: designer, guvnor, jBPM > Attachments: server.log > > > I want to use the jBPM Designer to create a BPMN2 process. It is in fact created (It is listed in the according package afterwards.) but when the new process should be opened and it's diagram be shown the screen remains stuck on showing the message "jBPM Web Designer loading. Please wait...". The same is true when I try to load existing BPMN2 processes from the repository (which I created using Firefox). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-673) Identify produckey and product line for Jaeger

by Gary Brown (Jira)

[ https://issues.jboss.org/browse/SWSQE-673?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SWSQE-673: ---------------------------------- Jaeger is part of the OpenShift Service Mesh product - so I guess it would share the same key/line - but best to confirm with [~rhn-coreos-bharring]. > Identify produckey and product line for Jaeger > ---------------------------------------------- > > Key: SWSQE-673 > URL: https://issues.jboss.org/browse/SWSQE-673 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Kevin Earls > Priority: Major > Labels: pqi > > We need the produckey for Jaeger > also which product line its map to? what is product hierarchy for these two products? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11918) Keycloak adapter broken because of missing org.jboss.metadata module

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11918?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-11918: ------------------------------ Labels: blocker-WF17 (was: ) > Keycloak adapter broken because of missing org.jboss.metadata module > -------------------------------------------------------------------- > > Key: WFLY-11918 > URL: https://issues.jboss.org/browse/WFLY-11918 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.0.Beta1 > Reporter: Simon Priadka > Assignee: Yeray Borges > Priority: Blocker > Labels: blocker-WF17 > > When trying to install keycloak-wildfly-subsystem described in [this guide|https://www.keycloak.org/docs/3.0/getting_started/topics/secure-jbo...], the install fails because of: > {code:java} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.modules.ModuleLoadError: org.jboss.metadata", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-673) Identify produckey and product line for Jaeger

by Kevin Earls (Jira)

[ https://issues.jboss.org/browse/SWSQE-673?page=com.atlassian.jira.plugin.... ] Kevin Earls commented on SWSQE-673: ----------------------------------- Hi [~objectiser] Do you know what Product Key and Product Line are for Jaeger? > Identify produckey and product line for Jaeger > ---------------------------------------------- > > Key: SWSQE-673 > URL: https://issues.jboss.org/browse/SWSQE-673 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Kevin Earls > Priority: Major > Labels: pqi > > We need the produckey for Jaeger > also which product line its map to? what is product hierarchy for these two products? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019