February 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3114) [5.9.4] LRA module should depend on a specific snapshot build

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3114: ---------------------------------- Affects Version/s: 5.9.3.Final (was: 5.9.2.Final) > [5.9.4] LRA module should depend on a specific snapshot build > ------------------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Martin Stefanko > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) [5.9.4] LRA module should depend on a specific snapshot build

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3114: ---------------------------------- Description: The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... Current version of the implementation is running against latest build: - api - 1.0-20190222.071200-278 - tck - 1.0-20190222.071201-278 was: The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). The current implementation was coded against the following maven snapshot: org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202 > [5.9.4] LRA module should depend on a specific snapshot build > ------------------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Martin Stefanko > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) [5.9.4] LRA module should depend on a specific snapshot build

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3114: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1413 > [5.9.4] LRA module should depend on a specific snapshot build > ------------------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Martin Stefanko > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) [5.9.4] LRA module should depend on a specific snapshot build

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3114: ------------------------------------- Summary: [5.9.4] LRA module should depend on a specific snapshot build Key: JBTM-3114 URL: https://issues.jboss.org/browse/JBTM-3114 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.2.Final Reporter: Martin Stefanko Assignee: Michael Musgrove Fix For: 5.9.3.Final The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). The current implementation was coded against the following maven snapshot: org.eclipse.microprofile.lra:microprofile-lra-api:1.0-20181217.132756-202 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3090) LRA TCK failures need to report more context to facilitate debugging

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3090?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-3090: --------------------------------------- [~mmusgrov] is this issue still relevant? I expect there could not enough information in the LRA TCK tests but just after refactoring it behaves a bit differently. So I'm just asking if this JIRA is not for to be reconsidered. > LRA TCK failures need to report more context to facilitate debugging > -------------------------------------------------------------------- > > Key: JBTM-3090 > URL: https://issues.jboss.org/browse/JBTM-3090 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test failure message reports > > failures.forEach(f -> System.out.printf("%s%n", f)); > where f is the failure reason. There is also a verbose option which prints out the stack trace where the failure was reported. But in some failure cases these two pieces of information are insufficient to debug the failure. It would be nice if the resources that participated in the test also logged information which could be reported for more effective analysis of the reasons for the failure. This last requirement may affect the TCK itself so the code in the eclipse microprofile-lra repo should be analysed as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3093) Disable the maven site plugin for the LRA module

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3093?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3093. ------------------------------- > Disable the maven site plugin for the LRA module > ------------------------------------------------ > > Key: JBTM-3093 > URL: https://issues.jboss.org/browse/JBTM-3093 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.3.Final > > > The narayana code coverage profile invokes the maven site goal so that the output can be viewed easily. > > Now LRA relies on microprofile-lra-api snapshot builds but the site plugin appears to resolve to the latest snapshot (rather than a particular snapshot build) and since microprofile-lra-api regularly undergoes changes there are compilation failures. > This JIRA proposes that we disable the site plugin for the LRA module. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3109) Refactoring LRA tck tests to comply with Arquillian refactoring in LRA spec

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3109?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-3109: --------------------------------- > Refactoring LRA tck tests to comply with Arquillian refactoring in LRA spec > --------------------------------------------------------------------------- > > Key: JBTM-3109 > URL: https://issues.jboss.org/browse/JBTM-3109 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.9.3.Final > > > The LRA specification started to use the Arquillian for running the TCK tests - see issue https://github.com/eclipse/microprofile-lra/issues/94 > The Narayana LRA client needs to comply with this change and the setup for startin the tests need to be refactored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3109) Refactoring LRA tck tests to comply with Arquillian refactoring in LRA spec

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3109?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-3109: -------------------------------- Issue Type: Task (was: Enhancement) > Refactoring LRA tck tests to comply with Arquillian refactoring in LRA spec > --------------------------------------------------------------------------- > > Key: JBTM-3109 > URL: https://issues.jboss.org/browse/JBTM-3109 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.9.3.Final > > > The LRA specification started to use the Arquillian for running the TCK tests - see issue https://github.com/eclipse/microprofile-lra/issues/94 > The Narayana LRA client needs to comply with this change and the setup for startin the tests need to be refactored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3109) Refactoring LRA tck tests to comply with Arquillian refactoring in LRA spec

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3109?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3109. ------------------------------- Resolution: Done > Refactoring LRA tck tests to comply with Arquillian refactoring in LRA spec > --------------------------------------------------------------------------- > > Key: JBTM-3109 > URL: https://issues.jboss.org/browse/JBTM-3109 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Major > Fix For: 5.9.3.Final > > > The LRA specification started to use the Arquillian for running the TCK tests - see issue https://github.com/eclipse/microprofile-lra/issues/94 > The Narayana LRA client needs to comply with this change and the setup for startin the tests need to be refactored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3113) LRA coordinator defines in depenedencies whole microprofile stack

by Tom Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3113?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-3113. ------------------------------- > LRA coordinator defines in depenedencies whole microprofile stack > ----------------------------------------------------------------- > > Key: JBTM-3113 > URL: https://issues.jboss.org/browse/JBTM-3113 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.9.3.Final > > > The LRA coordinator defines the depenendency on whole MicroProfile stack. That's not necessary as it uses JAX-RS and CDI. The depenencies needed up to that will be resolved by the Wfly Swarm/Thorntail runtime. If we define whole stack then Wfly Swarm loads to the runtime unnecessary dependencies which makes the fat jar bigger than it needs to be. Plus the start time the container could be lower when we use only the dependencies which are really needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2019