September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1657) Ensure whole project buildable on JDK 11

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1657?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1657: ---------------------------------- Fix Version/s: 1.7.0.CR2 (was: 1.7.0.CR1) > Ensure whole project buildable on JDK 11 > ---------------------------------------- > > Key: ELY-1657 > URL: https://issues.jboss.org/browse/ELY-1657 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Fix For: 1.7.0.CR2 > > > This may be blocked on when we can remove support for Java 8 - although we could consider a build with Java 11 to exclude the Java 8 classes if that is possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1669) Update Travis CI Configuration to use Java 10

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1669?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1669. ----------------------------------- Resolution: Done > Update Travis CI Configuration to use Java 10 > --------------------------------------------- > > Key: ELY-1669 > URL: https://issues.jboss.org/browse/ELY-1669 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.7.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1670) Release WildFly Elytron 1.7.0.CR1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1670?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1670. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.7.0.CR1 > --------------------------------- > > Key: ELY-1670 > URL: https://issues.jboss.org/browse/ELY-1670 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.7.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-421) Kiali Test Mesh support for ReplicationControllers and DeploymentConfig

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-421?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-421: ------------------------------------ Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Kiali Test Mesh support for ReplicationControllers and DeploymentConfig > ----------------------------------------------------------------------- > > Key: SWSQE-421 > URL: https://issues.jboss.org/browse/SWSQE-421 > Project: Kiali QE > Issue Type: Dev Task > Reporter: Lucas Ponce > Assignee: Guilherme Baufaker Rêgo > > Related to KIALI-1284, Kiali will support several types for deployments. > Currently, only Deployment objects are fully supported on list pages. > Also, to sync with the current OpenShift Web Console, we plan to support: Deployment, ReplicaSet, ReplicationController and DeploymentConfig (this one is not a kubernetes object, but only OpenShift one). > So, in order to help in the testing, Kiali Test Mesh could add these new types: ReplicationController and DeploymentConfig to deploy a test scenario that we can use for our testing. > I.e. > {code} > DEPLOYMENT_TYPE=ReplicaController NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle > DEPLOYMENT_TYPE=DeploymentConfig NUM_SERVICES=2 NUM_VERSIONS=2 make openshift-deploy-kiali-test-circle > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11041) Jaxws-retail quickstart readme file contains reference to EAP server

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-11041?page=com.atlassian.jira.plugin... ] Sande Gilda reassigned WFLY-11041: ---------------------------------- Assignee: Sande Gilda (was: Eduardo Martins) > Jaxws-retail quickstart readme file contains reference to EAP server > -------------------------------------------------------------------- > > Key: WFLY-11041 > URL: https://issues.jboss.org/browse/WFLY-11041 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sultan Zhantemirov > Assignee: Sande Gilda > > In the latest quickstarts build from [https://github.com/wildfly/quickstart|https://github.com/wildfly/quickstart] the line in jaxws-retail Readme > {noformat} > Select the JBoss EAP server and click Finish. > {noformat} > references to EAP in situation when it can mention a WildFly server on the beginning of Readme. > I suppose the server name in this line should be variable depending on EAP/WFLY distribution. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4118) Upgrade WildFly Elytron to 1.7.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-4118: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.7.0.CR1 Key: WFCORE-4118 URL: https://issues.jboss.org/browse/WFCORE-4118 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10615) Duplicate layer 'base' in integration/elytron testsuite

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10615?page=com.atlassian.jira.plugin... ] Jan Kalina closed WFLY-10615. ----------------------------- Resolution: Out of Date > Duplicate layer 'base' in integration/elytron testsuite > ------------------------------------------------------- > > Key: WFLY-10615 > URL: https://issues.jboss.org/browse/WFLY-10615 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 13.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > Testsuite wildfly/testsuite/integration/elytron has workarounded module path problem: > {code} > MSC000001: Failed to start service jboss.patching.manager: org.jboss.msc.service.StartException in service jboss.patching.manager: java.lang.IllegalStateException: Duplicate layer 'base' > at org.jboss.as.patching.installation.InstallationManagerService.start(InstallationManagerService.java:106) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Duplicate layer 'base' > at org.jboss.as.patching.installation.LayersFactory$ProcessedLayers.addLayer(LayersFactory.java:305) > at org.jboss.as.patching.installation.LayersFactory.processRoot(LayersFactory.java:182) > at org.jboss.as.patching.installation.LayersFactory.process(LayersFactory.java:127) > at org.jboss.as.patching.installation.LayersFactory.load(LayersFactory.java:86) > at org.jboss.as.patching.installation.InstallationManagerImpl.<init>(InstallationManagerImpl.java:47) > at org.jboss.as.patching.installation.InstallationManager.load(InstallationManager.java:185) > at org.jboss.as.patching.installation.InstallationManagerService.load(InstallationManagerService.java:128) > at org.jboss.as.patching.installation.InstallationManagerService.start(InstallationManagerService.java:63) > ... 8 more > {code} > This is currently workarounded using following in pom.xml: > {code} >  > <module.path>foo</module.path> > {code} > But this prevent using `org.jboss.as.test.module.util.TestModule`, as it try to put created module into "foo", which fails - adding tests using custom modules requires removing this workaround. > The reason is {{target/wildfly/modules}} is twice in {{module.path}} system property (when in InstallationManagerService): > {code} > /home/jkalina/work/wildfly/testsuite/integration/elytron/target/wildfly/modules: > /home/jkalina/work/wildfly/testsuite/integration/elytron/target/wildfly/modules: > /home/jkalina/work/wildfly/testsuite/integration/elytron/target/modules > {code} > Note: when reading {{module.path}} from the test (regardless RunAsClient is used or not), the value is correct: > {code} > /home/jkalina/work/wildfly/testsuite/integration/elytron/target/wildfly/modules: > /home/jkalina/work/wildfly/testsuite/integration/elytron/target/modules > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1670) Release WildFly Elytron 1.7.0.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1670: ------------------------------------- Summary: Release WildFly Elytron 1.7.0.CR1 Key: ELY-1670 URL: https://issues.jboss.org/browse/ELY-1670 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.7.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4111) Upgrade WildFly Elytron to 1.6.1.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4111?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4111: -------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Upgrade WildFly Elytron to 1.6.1.Final > -------------------------------------- > > Key: WFCORE-4111 > URL: https://issues.jboss.org/browse/WFCORE-4111 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4098) SimpleMapAttributeDefinition Values Unable to Reference Capability

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4098?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4098: -------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > SimpleMapAttributeDefinition Values Unable to Reference Capability > ------------------------------------------------------------------ > > Key: WFCORE-4098 > URL: https://issues.jboss.org/browse/WFCORE-4098 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 7.0.0.Alpha2 > > > Instead of the values being mapped to a capability the entire Map is converted to a String as the dynamic portion of the name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 September 2018