August 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3179) Release of narayana-jts-idlj does not contain source files in the -source artifact

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3179?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3179: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1487 > Release of narayana-jts-idlj does not contain source files in the -source artifact > ---------------------------------------------------------------------------------- > > Key: JBTM-3179 > URL: https://issues.jboss.org/browse/JBTM-3179 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Release Process > Affects Versions: 5.9.5.Final, 5.9.6.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > From time the {{-Pcommunity}} tag is used during the Narayana release the {{-source.jar}} artifact of {{narayana-jts-idlj}} and {{narayana-jts-ibmorb}} do not contain java source files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3179) Release of narayana-jts-idlj does not contain source files in the -source artifact

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3179: -------------------------------------- Summary: Release of narayana-jts-idlj does not contain source files in the -source artifact Key: JBTM-3179 URL: https://issues.jboss.org/browse/JBTM-3179 Project: JBoss Transaction Manager Issue Type: Bug Components: Release Process Affects Versions: 5.9.6.Final, 5.9.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka >From time the {{-Pcommunity}} tag is used during the Narayana release the {{-source.jar}} artifact of {{narayana-jts-idlj}} and {{narayana-jts-ibmorb}} do not contain java source files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3172) Failing CI tests on Windows - Catelyn JDK8

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3172?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed JBTM-3172. ---------------------------------- Resolution: Done The trouble was at Catelyn where Narayana CI runs the PR on shared workspace. The workspace contained a conflicting source code changes and rebase was failing. [~tomjenkinson] fixed the issue and from that time the CI runs smoothly. > Failing CI tests on Windows - Catelyn JDK8 > ------------------------------------------ > > Key: JBTM-3172 > URL: https://issues.jboss.org/browse/JBTM-3172 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Attachments: catelyn-build55-archive.zip, catelyn-build55-consoleText.txt > > > The Narayana CI for Windows fails with compilation failure on Catelyn. This failure occurs consistently but only on JDK8, not on JDK11. The failure is (see whole log console in attachment) > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0-jboss-2:compile (default-compile) on project jta: Compilation failure: Compilation failure: > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,1] illegal start of type > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,3] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,5] ';' expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[587,13] > expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,3] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,5] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[592,7] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,4] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,7] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,9] illegal start of expression > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,14] <identifier> expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,15] ';' expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,19] illegal start of type > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,31] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,50] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,63] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[594,77] <identifier> expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,13] = expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,14] ';' expected > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,132] illegal start of type > [ERROR] /C:/hudson/workspace/btny-pulls-narayana-catelyn/jdk/jdk8.latest/label/catelyn/ArjunaJTA/jta/classes/com/arjuna/ats/jta/logging/jtaI18NLogger.java:[595,157] ';' expected > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jta > {code} > When I run the compilation manually on Catelyn with JDK {{:\Progra~1\java\jdk1.8.0_20\bin\java.exe}} I have hit no issue either with compilation or with the testing. Maybe I run wrong JDK version or there is some another issue in involvement of Jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3116) Temporarily disable LRA quickstarts until the MP LRA spec is more stable

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3116?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-3116 at 8/21/19 5:22 AM: ----------------------------------------------------------------- The LRA quickstarts can be renabled now that 1.0.RC1 is available. The new PR is https://github.com/jbosstm/quickstart/pull/257 was (Author: mmusgrov): The LRA quickstarts can be renabled now that 1.0.RC1 is available. > Temporarily disable LRA quickstarts until the MP LRA spec is more stable > ------------------------------------------------------------------------ > > Key: JBTM-3116 > URL: https://issues.jboss.org/browse/JBTM-3116 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The MP LRA draft spec has recently undergone a lot of churn and we need to bring both the narayana implementation and the quickstarts into line with those changes. While that work is being undertaken the quickstarts should be disabled so that users and CI do not use non-working examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3116) Temporarily disable LRA quickstarts until the MP LRA spec is more stable

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3116?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3116: ---------------------------------------- The LRA quickstarts can be renabled now that 1.0.RC1 is available. > Temporarily disable LRA quickstarts until the MP LRA spec is more stable > ------------------------------------------------------------------------ > > Key: JBTM-3116 > URL: https://issues.jboss.org/browse/JBTM-3116 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The MP LRA draft spec has recently undergone a lot of churn and we need to bring both the narayana implementation and the quickstarts into line with those changes. While that work is being undertaken the quickstarts should be disabled so that users and CI do not use non-working examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3177) Rename lra-filters to narayana-lra

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3177?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3177: ---------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1485, https://github.com/jbosstm/quickstart/pull/256 (was: https://github.com/jbosstm/narayana/pull/1485) > Rename lra-filters to narayana-lra > ---------------------------------- > > Key: JBTM-3177 > URL: https://issues.jboss.org/browse/JBTM-3177 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.6.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > As lra-filters is the main (and only) dependency that users will typically come in contact with, it would be beneficial for it to have a generic name to avoid questions like why do I need to include lra-filters and not lra-client? It's easier to explain and read: > {code:xml} > <dependency> > <groupId>org.eclipse.microprofile.lra</groupId> > <artifactId>microprofile-lra-api</artifactId> > <version>1.0-RC1</version> > </dependency> > <dependency> > <groupId>org.jboss.narayana.rts</groupId> > <artifactId>narayana-lra</artifactId> > <version>5.9.6.Final</version> > </dependency> > {code} > While this can lead to unwanted questions: > {code:xml} > <dependency> > <groupId>org.eclipse.microprofile.lra</groupId> > <artifactId>microprofile-lra-api</artifactId> > <version>1.0-RC1</version> > </dependency> > <dependency> > <groupId>org.jboss.narayana.rts</groupId> > <artifactId>lra-filters</artifactId> > <version>5.9.6.Final</version> > </dependency> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3178) Log a warning on AbstractRecord creation failures

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3178?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1486 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Log a warning on AbstractRecord creation failures > ------------------------------------------------- > > Key: JBTM-3178 > URL: https://issues.jboss.org/browse/JBTM-3178 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.9.6.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When an AbstractRecord#create() fails it would be useful to log which record type and record class was being constructed. See linked job for an example of such a failure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3178) Log a warning on AbstractRecord creation failures

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3178: -------------------------------------- Summary: Log a warning on AbstractRecord creation failures Key: JBTM-3178 URL: https://issues.jboss.org/browse/JBTM-3178 Project: JBoss Transaction Manager Issue Type: Task Components: Transaction Core Affects Versions: 5.9.6.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next When an AbstractRecord#create() fails it would be useful to log which record type and record class was being constructed. See linked job for an example of such a failure. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3177) Rename lra-filters to narayana-lra

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3177: ------------------------------------- Summary: Rename lra-filters to narayana-lra Key: JBTM-3177 URL: https://issues.jboss.org/browse/JBTM-3177 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.6.Final Reporter: Martin Stefanko Assignee: Martin Stefanko As lra-filters is the main (and only) dependency that users will typically come in contact with, it would be beneficial for it to have a generic name to avoid questions like why do I need to include lra-filters and not lra-client? It's easier to explain and read: {code:xml} <dependency> <groupId>org.eclipse.microprofile.lra</groupId> <artifactId>microprofile-lra-api</artifactId> <version>1.0-RC1</version> </dependency> <dependency> <groupId>org.jboss.narayana.rts</groupId> <artifactId>narayana-lra</artifactId> <version>5.9.6.Final</version> </dependency> {code} While this can lead to unwanted questions: {code:xml} <dependency> <groupId>org.eclipse.microprofile.lra</groupId> <artifactId>microprofile-lra-api</artifactId> <version>1.0-RC1</version> </dependency> <dependency> <groupId>org.jboss.narayana.rts</groupId> <artifactId>lra-filters</artifactId> <version>5.9.6.Final</version> </dependency> {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3177) Rename lra-filters to narayana-lra

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3177?page=com.atlassian.jira.plugin.... ] Martin Stefanko updated JBTM-3177: ---------------------------------- Status: Pull Request Sent (was: Open) > Rename lra-filters to narayana-lra > ---------------------------------- > > Key: JBTM-3177 > URL: https://issues.jboss.org/browse/JBTM-3177 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.6.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > As lra-filters is the main (and only) dependency that users will typically come in contact with, it would be beneficial for it to have a generic name to avoid questions like why do I need to include lra-filters and not lra-client? It's easier to explain and read: > {code:xml} > <dependency> > <groupId>org.eclipse.microprofile.lra</groupId> > <artifactId>microprofile-lra-api</artifactId> > <version>1.0-RC1</version> > </dependency> > <dependency> > <groupId>org.jboss.narayana.rts</groupId> > <artifactId>narayana-lra</artifactId> > <version>5.9.6.Final</version> > </dependency> > {code} > While this can lead to unwanted questions: > {code:xml} > <dependency> > <groupId>org.eclipse.microprofile.lra</groupId> > <artifactId>microprofile-lra-api</artifactId> > <version>1.0-RC1</version> > </dependency> > <dependency> > <groupId>org.jboss.narayana.rts</groupId> > <artifactId>lra-filters</artifactId> > <version>5.9.6.Final</version> > </dependency> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2019