[JBoss JIRA] (WFLY-13271) Some of the quickstarts do not use the correct WildFly version
by James Perkins (Jira)
James Perkins created WFLY-13271:
------------------------------------
Summary: Some of the quickstarts do not use the correct WildFly version
Key: WFLY-13271
URL: https://issues.redhat.com/browse/WFLY-13271
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Reporter: James Perkins
Assignee: James Perkins
The {{org.wildfly.plugins:wildfly-maven-plugin}} is used in several of the quickstarts, but the incorrect WildFly version is used. In some cases it's not used at all which would default to the current version in jboss-stacks. In other cases it's using the {{version.widfly.bom}} which is set to 19.0.1.Final. That version of WildFly dos not exist.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13270) The org.wildfly:wildfly-client-all artefact incorrectly contains the Elytron CDI extension
by James Perkins (Jira)
James Perkins created WFLY-13270:
------------------------------------
Summary: The org.wildfly:wildfly-client-all artefact incorrectly contains the Elytron CDI extension
Key: WFLY-13270
URL: https://issues.redhat.com/browse/WFLY-13270
Project: WildFly
Issue Type: Bug
Components: Build System, MP JWT, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 20.0.0.Beta1
This means if the artefact is included in a deployment the JWT activation is incorrectly triggered but with some dependencies missing leading to an error such as the following.
{code}
09:46:44,391 WARN [org.jboss.modules.define] (MSC service thread 1-1) Failed to define class org.wildfly.security.mp.jwt.JWTCDIExtension in Module "deployment.XXXX.ear" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/wildfly/security/mp/jwt/JWTCDIExtension (Module "deployment.XXXX.ear" from Service Module Loader): io/smallrye/jwt/auth/cdi/SmallRyeJWTAuthCDIExtension
at java.lang.ClassLoader.defineClass1(ClassLoader.java)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13269) The org.wildfly:wildfly-client-all artefact incorrectly contains the Elytron CDI extension
by Darran Lofthouse (Jira)
Darran Lofthouse created WFLY-13269:
---------------------------------------
Summary: The org.wildfly:wildfly-client-all artefact incorrectly contains the Elytron CDI extension
Key: WFLY-13269
URL: https://issues.redhat.com/browse/WFLY-13269
Project: WildFly
Issue Type: Bug
Components: Build System, MP JWT, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 20.0.0.Beta1
This means if the artefact is included in a deployment the JWT activation is incorrectly triggered but with some dependencies missing leading to an error such as the following.
{code}
09:46:44,391 WARN [org.jboss.modules.define] (MSC service thread 1-1) Failed to define class org.wildfly.security.mp.jwt.JWTCDIExtension in Module "deployment.XXXX.ear" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/wildfly/security/mp/jwt/JWTCDIExtension (Module "deployment.XXXX.ear" from Service Module Loader): io/smallrye/jwt/auth/cdi/SmallRyeJWTAuthCDIExtension
at java.lang.ClassLoader.defineClass1(ClassLoader.java)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ELY-1850) CredentialStore API missing ability to check alias types
by Ahmed Haddad (Jira)
[ https://issues.redhat.com/browse/ELY-1850?page=com.atlassian.jira.plugin.... ]
Ahmed Haddad commented on ELY-1850:
-----------------------------------
ok thanks.
is the contributor status sth i can obtain currently ?
> CredentialStore API missing ability to check alias types
> --------------------------------------------------------
>
> Key: ELY-1850
> URL: https://issues.redhat.com/browse/ELY-1850
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Affects Versions: 1.10.0.CR3
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
>
> The credential store allows different types to be stored under the same alias, removal requires the type to be specified so the correct entry can be removed.
> However there is no way to list the types stored under a specific alias so unless you know how the store was populated it can be impossible to remove an alias.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13268) MP Fault Tolerance quickstart cannot resolve dependencies with wildlfy-microprofile BOM
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13268?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13268:
----------------------------------
Description:
[~tterem] discovered that MP FT QS guide is followed from its README, it wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
For example, the microprofile-fault-tolerance QS will fails with
{code}
[ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors
[ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21
[ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21
{code}
We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
was:
[~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
For example, the microprofile-fault-tolerance QS will fails with
{code}
[ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors
[ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21
[ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21
{code}
We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
> MP Fault Tolerance quickstart cannot resolve dependencies with wildlfy-microprofile BOM
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-13268
> URL: https://issues.redhat.com/browse/WFLY-13268
> Project: WildFly
> Issue Type: Bug
> Components: BOM, MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 19.0.1.Final, 20.0.0.Beta1
>
>
> [~tterem] discovered that MP FT QS guide is followed from its README, it wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
> For example, the microprofile-fault-tolerance QS will fails with
> {code}
> [ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors
> [ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21
> [ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21
> {code}
> We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13268) MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13268?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13268:
----------------------------------
Description:
[~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
For example, the microprofile-fault-tolerance QS will fails with
{code}
[ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors
[ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21
[ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21
{code}
We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
was:
[~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
For example, the microprofile-config QS will fails with
{code}
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 45, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 52, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-client:jar is missing. @ line 57, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.logging:commons-logging-jboss-logging:jar is missing. @ line 62, column 25
{code}
We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
> MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM
> ----------------------------------------------------------------------------------
>
> Key: WFLY-13268
> URL: https://issues.redhat.com/browse/WFLY-13268
> Project: WildFly
> Issue Type: Bug
> Components: BOM, MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 19.0.1.Final, 20.0.0.Beta1
>
>
> [~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
> For example, the microprofile-fault-tolerance QS will fails with
> {code}
> [ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors
> [ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21
> [ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21
> {code}
> We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13268) MP Fault Tolerance quickstart cannot resolve dependencies with wildlfy-microprofile BOM
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13268?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13268:
----------------------------------
Summary: MP Fault Tolerance quickstart cannot resolve dependencies with wildlfy-microprofile BOM (was: MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM)
> MP Fault Tolerance quickstart cannot resolve dependencies with wildlfy-microprofile BOM
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-13268
> URL: https://issues.redhat.com/browse/WFLY-13268
> Project: WildFly
> Issue Type: Bug
> Components: BOM, MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 19.0.1.Final, 20.0.0.Beta1
>
>
> [~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
> For example, the microprofile-fault-tolerance QS will fails with
> {code}
> [ERROR] The project org.wildfly.quickstart.microprofile.faulttolerance:microprofile-fault-tolerance:1.0-SNAPSHOT (/Users/rhusar/Desktop/REAL_QS/microprofile-fault-tolerance/pom.xml) has 2 errors
> [ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-jaxrs:jar is missing. @ line 34, column 21
> [ERROR] 'dependencies.dependency.version' for org.jboss.logging:jboss-logging:jar is missing. @ line 39, column 21
> {code}
> We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13268) MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13268?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13268:
----------------------------------
Component/s: (was: MP Config)
> MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM
> ----------------------------------------------------------------------------------
>
> Key: WFLY-13268
> URL: https://issues.redhat.com/browse/WFLY-13268
> Project: WildFly
> Issue Type: Bug
> Components: BOM, MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 19.0.1.Final, 20.0.0.Beta1
>
>
> [~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
> For example, the microprofile-config QS will fails with
> {code}
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 45, column 25
> [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 52, column 25
> [ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-client:jar is missing. @ line 57, column 25
> [ERROR] 'dependencies.dependency.version' for org.jboss.logging:commons-logging-jboss-logging:jar is missing. @ line 62, column 25
> {code}
> We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13268) MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13268?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13268:
----------------------------------
Description:
[~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
For example, the microprofile-config QS will fails with
{code}
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 45, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 52, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-client:jar is missing. @ line 57, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.logging:commons-logging-jboss-logging:jar is missing. @ line 62, column 25
{code}
We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
was:
[~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain commmong dependencies.
For example, the microprofile-config QS will fails with
{code}
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 45, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 52, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-client:jar is missing. @ line 57, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.logging:commons-logging-jboss-logging:jar is missing. @ line 62, column 25
{code}
We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
> MicroProfile quickstarts cannot resolve dependencies with wildlfy-microprofile BOM
> ----------------------------------------------------------------------------------
>
> Key: WFLY-13268
> URL: https://issues.redhat.com/browse/WFLY-13268
> Project: WildFly
> Issue Type: Bug
> Components: BOM, MP Config, MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Critical
> Fix For: 19.0.1.Final, 20.0.0.Beta1
>
>
> [~tterem] discovered that if QS guides are followed from their READMEs, they wont be able to resolve some dependencies. This is because we switched last minute to microprofile BOM which does not contain common dependencies.
> For example, the microprofile-config QS will fails with
> {code}
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] 'dependencies.dependency.version' for junit:junit:jar is missing. @ line 45, column 25
> [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ line 52, column 25
> [ERROR] 'dependencies.dependency.version' for org.jboss.resteasy:resteasy-client:jar is missing. @ line 57, column 25
> [ERROR] 'dependencies.dependency.version' for org.jboss.logging:commons-logging-jboss-logging:jar is missing. @ line 62, column 25
> {code}
> We need to either continue the disucssion what needs to be in the microprofile BOM or import the other BOM into QS-s.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month