[JBoss JIRA] (ELY-1966) (7.3.z) Elytron tool command execution fails with java.nio.file.NoSuchFileException
by Ilia Vassilev (Jira)
Ilia Vassilev created ELY-1966:
----------------------------------
Summary: (7.3.z) Elytron tool command execution fails with java.nio.file.NoSuchFileException
Key: ELY-1966
URL: https://issues.redhat.com/browse/ELY-1966
Project: WildFly Elytron
Issue Type: Bug
Components: Command-Line Tool
Affects Versions: 1.11.3.Final
Reporter: Ilia Vassilev
Assignee: Ricardo Martin Camarero
Fix For: 1.12.0.CR2
This is a regression in behavior of *elytron-tool.sh* with respect to 7.3.0.GA-CR4.
Basically, it was noticed that some commands involving a custom credential store returned a exit code of *0* and no error when executed against 7.3.0.GA-CR4 distribution, while the same commands are failing with various error codes against 7.4.0.CD19-CR1.
See _Steps to Reproduce_ for an example.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13473) Missing repositories in generated poms for MP QS in EAP
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13473?page=com.atlassian.jira.plugi... ]
Eduardo Martins reassigned WFLY-13473:
--------------------------------------
Assignee: Martin Stefanko (was: Eduardo Martins)
> Missing repositories in generated poms for MP QS in EAP
> -------------------------------------------------------
>
> Key: WFLY-13473
> URL: https://issues.redhat.com/browse/WFLY-13473
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Martin Stefanko
> Priority: Blocker
>
> The QS in EAP XP 1.0.0.GA-CR1 contain instructions that create project from scratch using mvn archetype. Such projects do not have repositories defined that are needed for QS and are defined in QS parent pom:
> {code}
> <repositories>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>${maven.repository.url}</url>
> <layout>default</layout>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-enterprise-maven-repository</id>
> <name>JBoss Enterprise Maven Repository</name>
> <url>${maven.redhat.repository.url}</url>
> <layout>default</layout>
> </repository>
> </repositories>
> {code}
> Without the repos defined, the BOMs and other dependencies that are not present in maven central won't be found.
> Affected QS:
> * microprofile-config
> * microprofile-fault-tolerance
> * microprofile-health
> * microprofile-jwt
> * microprofile-metrics
> * microprofile-openapi
> * microprofile-opentracing
> * microprofile-rest-client
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13473) Missing repositories in generated poms for MP QS in EAP
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13473?page=com.atlassian.jira.plugi... ]
Eduardo Martins updated WFLY-13473:
-----------------------------------
Summary: Missing repositories in generated poms for MP QS in EAP (was: Missing repositories in generated poms for MP QS in EAP XP1)
> Missing repositories in generated poms for MP QS in EAP
> -------------------------------------------------------
>
> Key: WFLY-13473
> URL: https://issues.redhat.com/browse/WFLY-13473
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Blocker
>
> The QS in EAP XP 1.0.0.GA-CR1 contain instructions that create project from scratch using mvn archetype. Such projects do not have repositories defined that are needed for QS and are defined in QS parent pom:
> {code}
> <repositories>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>${maven.repository.url}</url>
> <layout>default</layout>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-enterprise-maven-repository</id>
> <name>JBoss Enterprise Maven Repository</name>
> <url>${maven.redhat.repository.url}</url>
> <layout>default</layout>
> </repository>
> </repositories>
> {code}
> Without the repos defined, the BOMs and other dependencies that are not present in maven central won't be found.
> Affected QS:
> * microprofile-config
> * microprofile-fault-tolerance
> * microprofile-health
> * microprofile-jwt
> * microprofile-metrics
> * microprofile-openapi
> * microprofile-opentracing
> * microprofile-rest-client
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13473) Missing repositories in generated poms for MP QS in EAP XP1
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13473?page=com.atlassian.jira.plugi... ]
Eduardo Martins moved JBEAP-19497 to WFLY-13473:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13473 (was: JBEAP-19497)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Quickstarts
(was: Quickstarts)
Affects Version/s: (was: EAP-XP-1.0.0.GA-CR1)
> Missing repositories in generated poms for MP QS in EAP XP1
> -----------------------------------------------------------
>
> Key: WFLY-13473
> URL: https://issues.redhat.com/browse/WFLY-13473
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Blocker
>
> The QS in EAP XP 1.0.0.GA-CR1 contain instructions that create project from scratch using mvn archetype. Such projects do not have repositories defined that are needed for QS and are defined in QS parent pom:
> {code}
> <repositories>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>${maven.repository.url}</url>
> <layout>default</layout>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>never</updatePolicy>
> </snapshots>
> <id>jboss-enterprise-maven-repository</id>
> <name>JBoss Enterprise Maven Repository</name>
> <url>${maven.redhat.repository.url}</url>
> <layout>default</layout>
> </repository>
> </repositories>
> {code}
> Without the repos defined, the BOMs and other dependencies that are not present in maven central won't be found.
> Affected QS:
> * microprofile-config
> * microprofile-fault-tolerance
> * microprofile-health
> * microprofile-jwt
> * microprofile-metrics
> * microprofile-openapi
> * microprofile-opentracing
> * microprofile-rest-client
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13467) Issues in readme for microprofile-opentracing QS
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13467?page=com.atlassian.jira.plugi... ]
Eduardo Martins updated WFLY-13467:
-----------------------------------
Git Pull Request: https://github.com/wildfly/quickstart/pull/418, https://github.com/wildfly/quickstart/pull/421 (was: https://github.com/wildfly/quickstart/pull/418)
> Issues in readme for microprofile-opentracing QS
> ------------------------------------------------
>
> Key: WFLY-13467
> URL: https://issues.redhat.com/browse/WFLY-13467
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 19.1.0.Final
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
> Priority: Critical
> Fix For: 20.0.0.Beta1
>
>
> (1) The order of the steps at the beginning is confusing:
> 1. Solution section says to start EAP and deploy the QS
> 2. Start the JBoss EAP XP Standalone Server section says start EAP
> (2) Consider adding standard sections - see other (non-MP - because these were not yet tested)
> * Use of the EAP_HOME and QUICKSTART_HOME Variables
> * Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse
> (3) Consider adding some instructions (or link to later sections of the readme) to access the app when deploying the complete example, it is only shown in the step-by-step sections.
> (4) pom.xml changes show WF BOM instead of EAP one:
> {code}
> <groupId>org.wildfly.bom</groupId>
> <artifactId>wildfly-microprofile</artifactId>
> <version>${version.server.bom}</version>
> where ${version.server.bom} is the version of your JBoss EAP XP, in our case "1.0".
> {code}
> Please notice there's no WF BOM of version 1.0.
> (5) WildFly used instead of EAP in:
> {code}
> <!-- Import the CDI API, we use provided scope as the API is included in WildFly -->
> <!-- Import the Jakarta REST API, we use provided scope as the API is included in WildFly -->
> {code}
> The same references are used in pom.xml as well.
> (6) No spans are created in jaeger console as documented in sections {{Implicit tracing of REST resources}} and later. In fact, jaeger console does not show the {{microprofile-opentracing.war}} at all following the instructions in readme. This is due to missing env vars settings when starting the EAP server.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13463) Issues in readme for microprofile-metrics QS
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13463?page=com.atlassian.jira.plugi... ]
Eduardo Martins updated WFLY-13463:
-----------------------------------
Git Pull Request: https://github.com/wildfly/quickstart/pull/415, https://github.com/wildfly/quickstart/pull/419 (was: https://github.com/wildfly/quickstart/pull/415)
> Issues in readme for microprofile-metrics QS
> --------------------------------------------
>
> Key: WFLY-13463
> URL: https://issues.redhat.com/browse/WFLY-13463
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 19.1.0.Final
> Reporter: Martin Stefanko
> Assignee: Martin Stefanko
> Priority: Critical
> Fix For: 20.0.0.Beta1
>
>
> (1) pom.xml changes show WF BOM instead of EAP one:
> {code}
> <groupId>org.wildfly.bom</groupId>
> <artifactId>wildfly-microprofile</artifactId>
> <version>${version.server.bom}</version>
> where ${version.server.bom} is the version of your JBoss EAP XP, in our case "1.0".
> {code}
> Please notice there's no WF BOM of version 1.0.
> (2) {{WildFly}} used several times instead of {{JBoss EAP XP}} or simply {{server}}, e.g.:
> {code}
> <!-- Import the MicroProfile Metrics API, we use provided scope as the API is included in WildFly -->
> {code}
> This is also used in pom.xml.
> Some sentences use correct product name, e.g.:
> {code}
> Even without any direct interaction, JBoss EAP XP server already collects and exposes some metrics.
> {code}
> (3) I'm not sure if this sentence is correct: {{You can note that there are custom metrics exposed by the individual JBoss EAP XP subsystems which are prefixed by wildfly_ or jboss_.}} - when accessing the endpoint as documented with EAP XP, I only see {{jboss_}} prefix, no {{wildfly_}} ones. Please confirm this is correct.
> (4) I think there's mistake in {{You can test it be typing for instance application_org_quickstart_microprofile_metrics_PrimeNumberChecker_performedChecks_total as the query expression and executing this query.}} There's no such item. Should it be {{application_org_wildfly_quickstarts_microprofile_metrics_PrimeNumberChecker_performedChecks_total}}?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13472) Failing unit tests in microprofile-jwt quickstart
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13472?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-19496 to WFLY-13472:
-------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13472 (was: JBEAP-19496)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Quickstarts
(was: Quickstarts)
Affects Version/s: (was: EAP-XP-1.0.0.GA-CR1)
> Failing unit tests in microprofile-jwt quickstart
> -------------------------------------------------
>
> Key: WFLY-13472
> URL: https://issues.redhat.com/browse/WFLY-13472
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
>
> When running tests from microprofile-jwt quickstart they all fail:
> {noformat}
> [ERROR] JWTClientIT.testAuthenticated:112 Successful call expected:<200> but was:<404>
> [ERROR] JWTClientIT.testAuthorizationRequired:124 Authorization required expected:<403> but was:<404>
> [ERROR] JWTClientIT.testAuthorized:138 Successful call expected:<200> but was:<404>
> [ERROR] JWTClientIT.testClaimAccess:168 Successful call expected:<200> but was:<404>
> [ERROR] JWTClientIT.testHelloWorld:96 Successful call expected:<200> but was:<404>
> [ERROR] JWTClientIT.testMissingRole:154 Authorization Required expected:<403> but was:<404>
> {noformat}
> This is caused by unnecessary slash in path:
> {code:java}
> index 933f636..2134ba8 100644
> --- a/microprofile-jwt/src/test/java/org/wildfly/quickstarts/mpjwt/JWTClientIT.java
> +++ b/microprofile-jwt/src/test/java/org/wildfly/quickstarts/mpjwt/JWTClientIT.java
> @@ -52,7 +52,7 @@ import org.junit.runner.RunWith;
> @RunAsClient
> public class JWTClientIT {
>
> - private static final String ROOT_PATH = "/rest/Sample/";
> + private static final String ROOT_PATH = "rest/Sample/";
> private static final String HELLO_WORLD = "helloworld";
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months