April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-614) Kiali - Review and document usage of UMB

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-614?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-614: --------------------------------------- [~mmahoney] At this moment we are using only the following producer and consumer, * producer: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/view/Jaeger/job/jaeg... * Consumer: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/view/Jaeger/job/jaeg... Is the one are you looking? > Kiali - Review and document usage of UMB > ---------------------------------------- > > Key: SWSQE-614 > URL: https://issues.jboss.org/browse/SWSQE-614 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > We need to document how we use UMB. > * jenkins master configuration > * jobs which are consuming msgs > * which msgs are consumed > * which msgs are sent to UMS -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-676) Review Priority of Kiali Test Cases on Polarion

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-676?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-676. ------------------------------------------- Resolution: Done > Review Priority of Kiali Test Cases on Polarion > ----------------------------------------------- > > Key: SWSQE-676 > URL: https://issues.jboss.org/browse/SWSQE-676 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Priority: Major > Labels: pqi > > Some Test cases don't have right priority set on Polarion -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-677) Review Priority of Saturn Test Cases

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-677?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-677. ------------------------------------------- Resolution: Done > Review Priority of Saturn Test Cases > ------------------------------------ > > Key: SWSQE-677 > URL: https://issues.jboss.org/browse/SWSQE-677 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: pqi > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-200) License.txt missing

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-200?page=com.atlassian.jira.plugin.s... ] Eduardo Martins updated JBEE-200: --------------------------------- Git Pull Request: https://github.com/jboss/jboss-javaee-specs/pull/14 > License.txt missing > -------------------- > > Key: JBEE-200 > URL: https://issues.jboss.org/browse/JBEE-200 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-javaee-specs > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-200) License.txt missing

by Eduardo Martins (Jira)

Eduardo Martins created JBEE-200: ------------------------------------ Summary: License.txt missing Key: JBEE-200 URL: https://issues.jboss.org/browse/JBEE-200 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-javaee-specs Reporter: Eduardo Martins Assignee: Eduardo Martins -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3160) adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm)

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3160?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3160: ------------------------------------------- Fix Version/s: 7.21.0.Final (was: 7.20.0.Final) > adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm) > ------------------------------------------------------------ > > Key: DROOLS-3160 > URL: https://issues.jboss.org/browse/DROOLS-3160 > Project: Drools > Issue Type: Feature Request > Reporter: Michael Biarnes Kiefer > Assignee: Toni Rikkola > Priority: Major > Fix For: 7.21.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-2254?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-2254: ------------------------------------------- Fix Version/s: 7.21.0.Final (was: 7.20.0.Final) > Automate .proto files rebuild in pom.xml > ---------------------------------------- > > Key: DROOLS-2254 > URL: https://issues.jboss.org/browse/DROOLS-2254 > Project: Drools > Issue Type: Task > Components: tools > Affects Versions: 7.5.0.Final > Reporter: Dmitry Volodin > Assignee: Dmitry Volodin > Priority: Minor > Fix For: 7.21.0.Final > > > According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. > This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3569) Configure SonarCloud for Drools

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3569?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3569: ------------------------------------------- Fix Version/s: 7.21.0.Final (was: 7.20.0.Final) > Configure SonarCloud for Drools > ------------------------------- > > Key: DROOLS-3569 > URL: https://issues.jboss.org/browse/DROOLS-3569 > Project: Drools > Issue Type: Story > Components: build > Reporter: Radovan Synek > Assignee: Radovan Synek > Priority: Major > Fix For: 7.21.0.Final > > > Configure SonarCloud analysis of PRs in Drools repository. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-3702 at 4/3/19 6:26 AM: ---------------------------------------------------------------- [~tari_manga] I agree.. Other tools keep the {{FIXED}} (x, y) and clip the connector when it intercepts the node's boundary (whereas Stunner overlaps it, giving the reported issue). Ideally Stunner could also do the same for {{FIXED}} magnets. However considering that to be not an insignificant effort I found simply changing {{DMNMarshaller.setConnectionMagnets(..)}} to call {{setAuto(true)}} on the new connection magnets seems to give an improvement on the reported issue (and makes reopening a diagram authored in our editor behave the same as it did when first authored). See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] and [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...]. was (Author: manstis): [~tari_manga] I agree.. Other tools keep the {{FIXED}} (x, y) and clip the connector when it intercepts the node's boundary (whereas Stunner overlaps it, giving the reported issue). Ideally Stunner could also do the same for {{FIXED}} magnets however for the purpose of this JIRA I propose we default to AUTO when re-opening. However considering that to be a not insignificant effort I found simply changing {{DMNMarshaller.setConnectionMagnets(..)}} to call {{setAuto(true)}} on the new connection magnets seems to give an improvement on the reported issue (and makes reopening a diagram authored in our editor behave the same as it did when first authored). See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] and [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...]. > [Stunner] Arrows are incorrectly positioned when save-open diagram > ------------------------------------------------------------------ > > Key: DROOLS-3702 > URL: https://issues.jboss.org/browse/DROOLS-3702 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner > Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif > > > 1. Add a `Decision Node` > 2. Add a `Input Data Node` bellow `Decision Node` > 3. Connect `Input Data Node` to `Decision Node` > 4. Save > 5. Close > 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned. > I noticed this in DMN Showcase and in drools-wb. > And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3702) [Stunner] Arrows are incorrectly positioned when save-open diagram

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3702?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3702: ---------------------------------------- [~tari_manga] I agree.. Other tools keep the {{FIXED}} (x, y) and clip the connector when it intercepts the node's boundary (whereas Stunner overlaps it, giving the reported issue). Ideally Stunner could also do the same for {{FIXED}} magnets however for the purpose of this JIRA I propose we default to AUTO when re-opening. However considering that to be a not insignificant effort I found simply changing {{DMNMarshaller.setConnectionMagnets(..)}} to call {{setAuto(true)}} on the new connection magnets seems to give an improvement on the reported issue (and makes reopening a diagram authored in our editor behave the same as it did when first authored). See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] and [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...]. > [Stunner] Arrows are incorrectly positioned when save-open diagram > ------------------------------------------------------------------ > > Key: DROOLS-3702 > URL: https://issues.jboss.org/browse/DROOLS-3702 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Michael Anstis > Priority: Major > Labels: Stunner > Attachments: auto-magnets.gif, fixed-magnets.gif, process-designer-connectors-magnets-issues.png, weird_arrow.gif > > > 1. Add a `Decision Node` > 2. Add a `Input Data Node` bellow `Decision Node` > 3. Connect `Input Data Node` to `Decision Node` > 4. Save > 5. Close > 6. Open againThe arrow from `Input Data Node` to `Decision Node` will be at right of the `Decision Node` and if you move the `Input Data Node`, the arrow is not repositioned. > I noticed this in DMN Showcase and in drools-wb. > And if you add a new `Decision Node` and a new `Input Data Node`, without save and close, it behaves as expected. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 April 2019