February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3657) [DMN Designer] Highlight invalid DRGElements

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3657: -------------------------------------- Summary: [DMN Designer] Highlight invalid DRGElements Key: DROOLS-3657 URL: https://issues.jboss.org/browse/DROOLS-3657 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis Whenever a DMN file is validated (be it when the Project is compiled or via the Validate button on the toolbar) the DMN editor should highlight issues reported by the validation. This should include DRG nodes (on the graph view) or DRGElements (in the Boxed Expression, aka grid, view). The nature of the highlighting is to be defined; but probably consists of an orange background for warnings and red background for errors; possibly both with a warning triangle positioned somewhere. UX will need engaging for design proposals. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3515) [DMN Designer] Validation: Validate button should compile the DMN file and report issues

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3515?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3515: ----------------------------------- Summary: [DMN Designer] Validation: Validate button should compile the DMN file and report issues (was: [DMN Designer] Validation does not check feel expressions.) > [DMN Designer] Validation: Validate button should compile the DMN file and report issues > ---------------------------------------------------------------------------------------- > > Key: DROOLS-3515 > URL: https://issues.jboss.org/browse/DROOLS-3515 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Thomas Mantegazzi > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2019-01-14-09-24-07-415.png, image-2019-01-14-09-25-01-777.png, image-2019-01-14-09-25-16-907.png > > > The "validate" button at the top does nit seem to be validating feel expressions: > !image-2019-01-14-09-24-07-415.png|thumbnail! > The input of this Decision is a "person" object: > !image-2019-01-14-09-25-01-777.png|thumbnail! > and this is the DRG: > !image-2019-01-14-09-25-16-907.png|thumbnail! > The validation should say that this literal expression is not valid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1976) [DMN Editor] Unique node names

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1976?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1976. ------------------------------------ Fix Version/s: 7.18.0.Final Resolution: Done > [DMN Editor] Unique node names > ------------------------------ > > Key: DROOLS-1976 > URL: https://issues.jboss.org/browse/DROOLS-1976 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: reported-by-qe > Fix For: 7.18.0.Final > > > According to the DMN specification, all node names represents also variable names, thus it is needed to enforce unique node name in the DRD diagram. > h2. Acceptance criteria > - Verify if DMN editor enforce unique node names -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1957) [DMN Editor] Syntax validation

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1957?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1957. ------------------------------------ Fix Version/s: 7.18.0.Final Resolution: Done > [DMN Editor] Syntax validation > ------------------------------ > > Key: DROOLS-1957 > URL: https://issues.jboss.org/browse/DROOLS-1957 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: reported-by-qe > Fix For: 7.18.0.Final > > > The DMN editor should support syntax validation, it means if the generated XML can be compiled. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1967) [DMN Editor] Structure validation

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1967?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1967. ------------------------------------ Fix Version/s: 7.18.0.Final Resolution: Done > [DMN Editor] Structure validation > --------------------------------- > > Key: DROOLS-1967 > URL: https://issues.jboss.org/browse/DROOLS-1967 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: reported-by-qe > Fix For: 7.18.0.Final > > > The DMN validation should reveal errors like missing connection. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-603) Migrate Jenkins2 CI Pipeline to Centra CI

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-603?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-603: ------------------------------- Sprint: Kiali Sprint #18 > Migrate Jenkins2 CI Pipeline to Centra CI > ------------------------------------------ > > Key: SWSQE-603 > URL: https://issues.jboss.org/browse/SWSQE-603 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-603) Migrate Jenkins2 CI Pipeline to Centra CI

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-603?page=com.atlassian.jira.plugin.... ] Matt Mahoney reassigned SWSQE-603: ---------------------------------- Assignee: Matt Mahoney (was: Michael Foley) > Migrate Jenkins2 CI Pipeline to Centra CI > ------------------------------------------ > > Key: SWSQE-603 > URL: https://issues.jboss.org/browse/SWSQE-603 > Project: Kiali QE > Issue Type: Story > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-605: ---------------------------------- Summary: Establish Central CI Jenkins Master For Kiali Key: SWSQE-605 URL: https://issues.jboss.org/browse/SWSQE-605 Project: Kiali QE Issue Type: Sub-task Reporter: Matt Mahoney Assignee: Matt Mahoney Our team at one time was allocated a Central CI Jenkins Master. Therefore, one of the following, Either: a) Confirm that our team's Central CI Jenkins Master is still available and usable Or b) Establish a new Central CI Jenkins Master -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11716) Deployment Fails with @Transactional in Passivating Scope Bean

by Matej Novotny (Jira)

[ https://issues.jboss.org/browse/WFLY-11716?page=com.atlassian.jira.plugin... ] Matej Novotny commented on WFLY-11716: -------------------------------------- Fix can look something like [this|https://github.com/manovotn/narayana/tree/wfly11716] (not turning it into PR since I didn't have time to test it yet). > Deployment Fails with @Transactional in Passivating Scope Bean > -------------------------------------------------------------- > > Key: WFLY-11716 > URL: https://issues.jboss.org/browse/WFLY-11716 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Beta1 > Environment: Java 8, Ubuntu Xenial > Reporter: Cody Lerum > Assignee: Brian Stansberry > Priority: Major > Attachments: jsf-npe.zip > > > On Wildfly 16.0.0.Beta1 deployment fails > {code} > org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001477: The bean Managed Bean [class co.cfly.oss.lerg.rateCenter.inventoryRequest.InventoryRequestView] with qualifiers [@Default @Any @Named] declares a passivating scope but has a(n) Interceptor [class com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired intercepts @Transactional] with a non-passivation-capable dependency com.arjuna.ats.jta.cdi.JNDIBean@12e2cb9f > at org.jboss.weld.bootstrap.Validator.validateInterceptorDecoratorInjectionPointPassivationCapable(Validator.java:480) > at org.jboss.weld.bootstrap.Validator.validateInterceptors(Validator.java:225) > at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:175) > at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526) > at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64) > at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1781) Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-1781?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer commented on DROOLS-1781: ------------------------------------------------ [~mcimbale] This PR is on "stand by" status. It should should not be merged. Once RHPAM/RHDM 7.3 CR1 and community 7.18.0.Final are out I will continue working on this. It runs locally, but I don't know if all these "filters" are necessary. I expect this con be done otherwise. > Investigate possible replacement of findbugs-maven-plugin with spotbugs-maven-plugin > ------------------------------------------------------------------------------------ > > Key: DROOLS-1781 > URL: https://issues.jboss.org/browse/DROOLS-1781 > Project: Drools > Issue Type: Task > Components: build > Affects Versions: 7.4.1.Final > Reporter: Petr Široký > Assignee: Michael Biarnes Kiefer > Priority: Major > Labels: java9 > > SpotBugs is a successor of FingBugs and as such uses different groupId + artifactId for maven plugin. It should also be compatible with Java 9 (at least in the latest versions). We need to investigate it the switch is painless and if so, do it. Otherwise we need to figure out what the blockers are and slowly start to fix them as FindBugs itself won't bet any more updates it seems and so won't be Java 9 compatible. > *How to migrate* > * Replace > {code} > <groupId>org.codehaus.mojo</groupId> > <artifactId>findbugs-maven-plugin</artifactId> > {code} > by > {code} > <groupId>com.github.spotbugs</groupId> > <artifactId>spotbugs-maven-plugin</artifactId> > {code} > * Look for all "findbugs" and replace it by "spotbugs" > ** Except for anything related to the findbugs annotations dependency that some dependencies drag in or exclude. Leave that one alone! > ** For example, change findbugs-check -> spotbugs-check, ... > * Merge this PR if it hasn't been merged already: https://github.com/kiegroup/optaplanner-wb/pull/320 > * Then you only need to adjust the following repo's: build-boostrap, drools, optaplanner and kie-wb-distributions. > ** See https://github.com/search?q=org%3Akiegroup+findbugs-maven-plugin&type=Code > ** Ignore contributed experiments, that repo is dead -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 February 2019