August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1651) Release WildFly Elytron 1.6.0.Final

by Darran Lofthouse (JIRA)

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

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4055) Activate jdk.unsupported module on modular JDK by default

by Richard Opalka (JIRA)

Richard Opalka created WFCORE-4055: -------------------------------------- Summary: Activate jdk.unsupported module on modular JDK by default Key: WFCORE-4055 URL: https://issues.jboss.org/browse/WFCORE-4055 Project: WildFly Core Issue Type: Bug Components: Management, Security, Server, Test Suite Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 6.0.0.CR3 WildFlySecurityManager uses sun.misc.Unsafe. Unsafe works only with jdk.unsupported module enabled. jdk.unsupported is not resolved by default so we need to activate it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-13) Enable constrain driven auth mode during deployment

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created ELYWEB-13: ---------------------------------------------- Summary: Enable constrain driven auth mode during deployment Key: ELYWEB-13 URL: https://issues.jboss.org/browse/ELYWEB-13 Project: Elytron Web Issue Type: Bug Affects Versions: 1.2.1.Final Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko Read authentication mode property from deployment info in AuthenticationManager -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2784) CSS for test "expression builder" dock tab design

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2784?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-2784: ------------------------------------------ [~srambach] Hi Sarah - two questions: 1) are all the css classes available in our drools-wb-webapp environment? For example, I see class="kie-dock__heading" and class="kie-dock__divider". 2) are the id mandatory as they are, or they may be generated at runtime (as long as they are unique) ? > CSS for test "expression builder" dock tab design > ------------------------------------------------- > > Key: DROOLS-2784 > URL: https://issues.jboss.org/browse/DROOLS-2784 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-24 at 9.19.37 AM.png, Screen Shot 2018-07-27 at 12.41.52 PM.png > > > As a practitioner I want to the option to an expression builder within the UI to: > - search for and select from a set of hierarchical Data Objects > - set conditions > - name variables > so that I can add these selections as Given/Expect input values when creating a scenario test outline. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles. > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476075, and: > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10894) [WFLY] enable constraint drive authentication mode for elytron

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-10894?page=com.atlassian.jira.plugin... ] Bartosz Spyrko-Śmietanko moved JBEAP-15288 to WFLY-10894: --------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10894 (was: JBEAP-15288) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security Web (Undertow) (was: Security) (was: Web (Undertow)) Affects Version/s: (was: 7.1.3.GA) Fix Version/s: (was: 7.1.5.GA) > [WFLY] enable constraint drive authentication mode for elytron > -------------------------------------------------------------- > > Key: WFLY-10894 > URL: https://issues.jboss.org/browse/WFLY-10894 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Labels: test_included > > Integration code for JBEAP-15054 > ---- > When elytron is enabled constraint driven authentication method (i.e. proactive-authentication=false) has no effect. > If you try to request an unsecured page sending in an invalid user with basic authentication, you should get the page returned with constraint drive authentication and a 401 with proactive authentication. This is what happens without Elytron enabled. But if you enable Elytron it gives a 401 in both cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4001) Eliminate --illegal-access option from WildFly

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4001?page=com.atlassian.jira.plugi... ] Richard Opalka commented on WFCORE-4001: ---------------------------------------- I'm going to test it further on all modular JDKs but it seems *--illegal-access=permit* option is not needed (by default) at all to pass our test suite [~brian.stansberry] > Eliminate --illegal-access option from WildFly > ---------------------------------------------- > > Key: WFCORE-4001 > URL: https://issues.jboss.org/browse/WFCORE-4001 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2905) UX design for the contextual menu

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2905?page=com.atlassian.jira.plugi... ] Gabriele Cardosi reassigned DROOLS-2905: ---------------------------------------- Assignee: Liz Clayton (was: Gabriele Cardosi) > UX design for the contextual menu > --------------------------------- > > Key: DROOLS-2905 > URL: https://issues.jboss.org/browse/DROOLS-2905 > Project: Drools > Issue Type: Sub-task > Reporter: Juraj Soltes > Assignee: Liz Clayton > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4001) Eliminate --illegal-access option from WildFly

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4001?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4001: ----------------------------------- Summary: Eliminate --illegal-access option from WildFly (was: --illegal-access should be allowed also in domain servers) > Eliminate --illegal-access option from WildFly > ---------------------------------------------- > > Key: WFCORE-4001 > URL: https://issues.jboss.org/browse/WFCORE-4001 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 6.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10876) Align jar file provided for MP OpenTracing into right modules

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10876?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10876: -------------------------------------- [~juraci.costa] I may have time to have a look. I'm not a CDI expert, but I think we should be able to figure it out. > Align jar file provided for MP OpenTracing into right modules > ------------------------------------------------------------- > > Key: WFLY-10876 > URL: https://issues.jboss.org/browse/WFLY-10876 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Juraci Paixão Kröhling > Priority: Critical > > With recent addition of MicroProfile OpenTracing implementation we currently have following set of jar files that are in the build to provide various MicroProfile features: > {code} > $ find modules | grep smallrye | grep jar$ | xargs ls -hl > -rw-rw-r--. 1 jstourac jstourac 39K Aug 16 15:13 modules/system/layers/base/io/smallrye/config/main/smallrye-config-1.3.3.jar > -rw-rw-r--. 1 jstourac jstourac 8.9K Aug 16 15:13 modules/system/layers/base/io/smallrye/health/main/smallrye-health-1.0.2.jar > -rw-rw-r--. 1 jstourac jstourac 38K Aug 16 15:13 modules/system/layers/base/org/wildfly/extension/microprofile/config-smallrye/main/wildfly-microprofile-config-smallrye-14.0.0.CR1-SNAPSHOT.jar > -rw-rw-r--. 1 jstourac jstourac 27K Aug 16 15:13 modules/system/layers/base/org/wildfly/extension/microprofile/health-smallrye/main/wildfly-microprofile-health-smallrye-14.0.0.CR1-SNAPSHOT.jar > -rw-rw-r--. 1 jstourac jstourac 228K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/gson-2.8.2.jar > -rw-rw-r--. 1 jstourac jstourac 123K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-core-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 2.8M Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > -rw-rw-r--. 1 jstourac jstourac 14K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-api-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 7.5K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-concurrent-0.1.0.jar > -rw-rw-r--. 1 jstourac jstourac 41K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-jaxrs2-0.1.6.jar > -rw-rw-r--. 1 jstourac jstourac 11K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-noop-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 7.4K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-tracerresolver-0.1.5.jar > -rw-rw-r--. 1 jstourac jstourac 7.9K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-util-0.31.0.jar > -rw-rw-r--. 1 jstourac jstourac 13K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-web-servlet-filter-0.1.0.jar > -rw-rw-r--. 1 jstourac jstourac 5.4K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/smallrye-opentracing-1.1.1.jar > -rw-rw-r--. 1 jstourac jstourac 11K Aug 16 15:13 modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar > {code} > It looks like the opentracing-smallrye module could be split up into a few separate modules. There at least two motivations: > # particular implementation into its own module separate from the e.g. microprofile specification > # because of the way how current patching mechanism works in WildFly, if we leave current {{opentracing-smallrye}} module as is, in case of a one-off patch it would mean to replace all files in the module - currently 3.3MB: > {code} > $ du -h modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/ > 3.3M modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/ > {code} > My proposal how to align the jar files is following: > # jaeger specific files should go into separate jaeger module > # {{wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar}} should be moved to new {{modules/system/layers/base/org/wildfly/extension/microprofile/opentracing-smallrye}} module so it matches what is done for {{health-smallrye}} and {{config-smallrye}} in extension subdir > # {{smallrye-opentracing-1.1.1.jar}} should be moved to {{base/io}} as is done for {{config}} and {{health}} - {{modules/system/layers/base/io/smallrye/opentracing/main/smallrye-opentracing-1.1.1.jar}} > # what about that {{gson-2.8.2.jar}} dependency? Shall it be moved to some more generic place? > This would give us following structure: > {code} > modules/system/layers/base/io/smallrye/config/main/smallrye-config-1.3.3.jar > modules/system/layers/base/io/smallrye/health/main/smallrye-health-1.0.2.jar > modules/system/layers/base/io/smallrye/opentracing/main/smallrye-opentracing-1.1.1.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-api-0.31.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-jaxrs2-0.1.6.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-concurrent-0.1.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-web-servlet-filter-0.1.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-noop-0.31.0.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-tracerresolver-0.1.5.jar > modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/opentracing-util-0.31.0.jar > modules/system/layers/base/org/wildfly/extension/microprofile/health-smallrye/main/wildfly-microprofile-health-smallrye-14.0.0.CR1-SNAPSHOT.jar > modules/system/layers/base/org/wildfly/extension/microprofile/config-smallrye/main/wildfly-microprofile-config-smallrye-14.0.0.CR1-SNAPSHOT.jar > modules/system/layers/base/org/wildfly/extension/microprofile/opentracing-smallrye/main/wildfly-microprofile-opentracing-smallrye-14.0.0.CR1-SNAPSHOT.jar > ---- I have no idea how this module for jaeger should be named... > modules/system/layers/base/org/wildfly/microprofile/jaeger/opentracing-smallrye/main/jaeger-thrift-0.30.4.jar > modules/system/layers/base/org/wildfly/microprofile/jaeger/opentracing-smallrye/main/jaeger-core-0.30.4.jar > ---- I have no idea how this module for gson should be named... > modules/system/layers/base/org/wildfly/gson/main/gson-2.8.2.jar > {code} > One additional piece for consideration - maybe we should also split up jar files that are just the microprofile-opentracing specification (api at least I guess) apart from the others in the {{modules/system/layers/base/org/wildfly/microprofile/opentracing-smallrye/main/}} > What do you think? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2862) Implement add row/ add column commands

by Gabriele Cardosi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2862?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-2862. ------------------------------------ Resolution: Done > Implement add row/ add column commands > -------------------------------------- > > Key: DROOLS-2862 > URL: https://issues.jboss.org/browse/DROOLS-2862 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Labels: ScenarioSimulation > Original Estimate: 1 day > Remaining Estimate: 1 day > > Implements command to add row/column. > For the moment being, they should not be mapped to specific "header" contextual menu items -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018