October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ] Michal Jurc updated WFLY-11226: ------------------------------- Labels: java11 (was: ) > Maven Wildfly plugin should be working with Java 9+ > --------------------------------------------------- > > Key: WFLY-11226 > URL: https://issues.jboss.org/browse/WFLY-11226 > Project: WildFly > Issue Type: Bug > Reporter: Michal Jurc > Assignee: James Perkins > Priority: Blocker > Labels: java11 > > The plugin needs to be reviewed and ensured it works with Java 9+. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ] Michal Jurc updated WFLY-11226: ------------------------------- Priority: Blocker (was: Major) > Maven Wildfly plugin should be working with Java 9+ > --------------------------------------------------- > > Key: WFLY-11226 > URL: https://issues.jboss.org/browse/WFLY-11226 > Project: WildFly > Issue Type: Bug > Reporter: Michal Jurc > Assignee: James Perkins > Priority: Blocker > > The plugin needs to be reviewed and ensured it works with Java 9+. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11226) Maven Wildfly plugin should be working with Java 9+

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFLY-11226?page=com.atlassian.jira.plugin... ] Michal Jurc moved WFMP-103 to WFLY-11226: ----------------------------------------- Project: WildFly (was: WildFly Maven Plugin) Key: WFLY-11226 (was: WFMP-103) Issue Type: Bug (was: Task) Workaround Description: Add {{<java-opts>--add-modules=java.se</java-opts>}} to plugin configuration Workaround: Workaround Exists Fix Version/s: (was: 1.3.0.Alpha1) > Maven Wildfly plugin should be working with Java 9+ > --------------------------------------------------- > > Key: WFLY-11226 > URL: https://issues.jboss.org/browse/WFLY-11226 > Project: WildFly > Issue Type: Bug > Reporter: Michal Jurc > Assignee: James Perkins > Priority: Major > > The plugin needs to be reviewed and ensured it works with Java 9+. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3058) [DMN Designer] Decision Navigator dock is shown for other stunner designers

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3058?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3058: -------------------------------- Summary: [DMN Designer] Decision Navigator dock is shown for other stunner designers (was: [DMN Designer] Decision Navigator dock is shown for business process) > [DMN Designer] Decision Navigator dock is shown for other stunner designers > --------------------------------------------------------------------------- > > Key: DROOLS-3058 > URL: https://issues.jboss.org/browse/DROOLS-3058 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2018-10-01 10-04-33.png > > > DMN model designer shows additional *Decision Navigator* dock next to *Project Explorer*. The issue is this additional dock remains opened also for business process. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3058) [DMN Designer] Decision Navigator dock is shown for other stunner designers

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3058?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3058: -------------------------------- Description: DMN model designer shows additional *Decision Navigator* dock next to *Project Explorer*. The issue is this additional dock remains opened also for *business process* or *scenario simulation*. (was: DMN model designer shows additional *Decision Navigator* dock next to *Project Explorer*. The issue is this additional dock remains opened also for business process.) > [DMN Designer] Decision Navigator dock is shown for other stunner designers > --------------------------------------------------------------------------- > > Key: DROOLS-3058 > URL: https://issues.jboss.org/browse/DROOLS-3058 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.13.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2018-10-01 10-04-33.png > > > DMN model designer shows additional *Decision Navigator* dock next to *Project Explorer*. The issue is this additional dock remains opened also for *business process* or *scenario simulation*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3171) [DMN Designer] Header selection after nested expression cell was selected

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3171: ----------------------------------- Summary: [DMN Designer] Header selection after nested expression cell was selected Key: DROOLS-3171 URL: https://issues.jboss.org/browse/DROOLS-3171 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-10-23 09-39-11.png, Screenshot from 2018-10-23 09-39-15.png, Screenshot from 2018-10-23 09-39-44.png, Screenshot from 2018-10-23 09-39-48.png The issue is reproducible for *invocation* and *function* if one of those contains some nested expression editor you can reproduce the issue as: - Select a cell of that nested editor - Click to header row of the parent editor - Blue rectangle outline will be rendered in strange way -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3171) [DMN Designer] Header selection after nested expression cell was selected

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3171?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3171: -------------------------------- Issue Type: Bug (was: Enhancement) Priority: Minor (was: Major) > [DMN Designer] Header selection after nested expression cell was selected > ------------------------------------------------------------------------- > > Key: DROOLS-3171 > URL: https://issues.jboss.org/browse/DROOLS-3171 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2018-10-23 09-39-11.png, Screenshot from 2018-10-23 09-39-15.png, Screenshot from 2018-10-23 09-39-44.png, Screenshot from 2018-10-23 09-39-48.png > > > The issue is reproducible for *invocation* and *function* if one of those contains some nested expression editor you can reproduce the issue as: > - Select a cell of that nested editor > - Click to header row of the parent editor > - Blue rectangle outline will be rendered in strange way -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2723) [DMN Designer] Ensure all cells are selected during autoedit

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2723?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2723: -------------------------------- Description: Different expression editors supports autoedit feature for specific cells when added row or column. As part of the linked epic, we have to ensure autoedit feature select the cell even if that is placed in header of the table. h2. Manual acceptance test Autoedit feature select header cell - Relation (/) - Decision Table (x) -- Add new column, header cell not selected - Invocation (/) - Context (/) was:Different expression editors supports autoedit feature for specific cells when added row or column. As part of the linked epic, we have to ensure autoedit feature select the cell even if that is placed in header of the table. > [DMN Designer] Ensure all cells are selected during autoedit > ------------------------------------------------------------ > > Key: DROOLS-2723 > URL: https://issues.jboss.org/browse/DROOLS-2723 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Different expression editors supports autoedit feature for specific cells when added row or column. As part of the linked epic, we have to ensure autoedit feature select the cell even if that is placed in header of the table. > h2. Manual acceptance test > Autoedit feature select header cell > - Relation (/) > - Decision Table (x) > -- Add new column, header cell not selected > - Invocation (/) > - Context (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3099) Add advanced column properties

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3099?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3099: -------------------------------------- [~uxdlc], more details can be found in [this|https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc0...] document (the original Test Scenarios (Preview) MVP requirements). Better description of the required, default, and hidden columns follows. * A *required* column is mandatory and cannot be removed from the table. * If a column is considered to be *default*, it's cells in the table rows contain predefined "default" values. Thus there must be the possibility to specify the default values for the column. * A *hidden* column can be completely hidden from the table and displayed again per user request. An example of such column is a column with default values, which does not have to be altered; in this case, the column can be hidden. Is this description sufficient? > Add advanced column properties > ------------------------------ > > Key: DROOLS-3099 > URL: https://issues.jboss.org/browse/DROOLS-3099 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > > As user I want to be able to specify advanced column properties like hidden, required and default value -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM

by Rostislav Svoboda (Jira)

[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-11178: ------------------------------------------ [~msvehla] how should we proceed with this issue ? > WSTrustTestCase failing on IBM > ------------------------------ > > Key: WFLY-11178 > URL: https://issues.jboss.org/browse/WFLY-11178 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Attachments: log.txt > > > As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is: > {code:java} > Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found > at javax.xml.validation.SchemaFactory.newInstance(Unknown Source) > at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94) > at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91) > at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75) > at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308) > at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120) > ... 102 more > {code} > It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 9 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 October 2018