July 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2226?page=com.atlassian.jira.plugin.... ] Michael Musgrove reassigned JBTM-2226: -------------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Issue with MAVEN_OPTS on Debian > ------------------------------- > > Key: JBTM-2226 > URL: https://issues.jboss.org/browse/JBTM-2226 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.2 > Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Minor > > MAVEN_OPTS unset > mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore > ./build.sh: 42: ./build.sh: [[: not found -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2226?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2226: ----------------------------------- BTW the build proceeds fine. It's just various warnings when, presumably, the variable(s) is(are) null. Maybe better error handling within the script? > Issue with MAVEN_OPTS on Debian > ------------------------------- > > Key: JBTM-2226 > URL: https://issues.jboss.org/browse/JBTM-2226 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.2 > Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > > MAVEN_OPTS unset > mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore > ./build.sh: 42: ./build.sh: [[: not found -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2226?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2226: ----------------------------------- It's dash on the version of Debian I'm using. > Issue with MAVEN_OPTS on Debian > ------------------------------- > > Key: JBTM-2226 > URL: https://issues.jboss.org/browse/JBTM-2226 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.2 > Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > > MAVEN_OPTS unset > mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore > ./build.sh: 42: ./build.sh: [[: not found -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2226?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2226: ---------------------------------------- The build script relies on bash being the default shell. So on debian /bin/sh must be resolving to something other than bash. What is the debian default shell (ie what does ps -p $$ report). The only solution I can think of is to update build.sh to check that the default script is bash and if not then exit with an error. And in the README explain that the user either needs to update build.sh to refer to bash or we give him a build command line that does not require build.sh. > Issue with MAVEN_OPTS on Debian > ------------------------------- > > Key: JBTM-2226 > URL: https://issues.jboss.org/browse/JBTM-2226 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.2 > Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > > MAVEN_OPTS unset > mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore > ./build.sh: 42: ./build.sh: [[: not found -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2226) Issue with MAVEN_OPTS on Debian

by Mark Little (JIRA)

Mark Little created JBTM-2226: --------------------------------- Summary: Issue with MAVEN_OPTS on Debian Key: JBTM-2226 URL: https://issues.jboss.org/browse/JBTM-2226 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 5.0.2 Environment: Linux debian 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux Reporter: Mark Little Assignee: Tom Jenkinson Priority: Minor MAVEN_OPTS unset mark@debian:~/Desktop/narayana$ ./build.sh -am -l :arjunacore ./build.sh: 42: ./build.sh: [[: not found -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2224) Move Compensations dependency adder to transactions subsytem

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2224?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-2224: ------------------------------------- For discussion: https://community.jboss.org/message/881063#881063 > Move Compensations dependency adder to transactions subsytem > ------------------------------------------------------------ > > Key: JBTM-2224 > URL: https://issues.jboss.org/browse/JBTM-2224 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Application Server Integration, TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.3 > > > The Compensating transactions API can now be used in standalone.xml as well as standalone-xts.xml. XTS is now only needed for distributed compensating transactions. > Therefore, it would be better to move the automatic dependency adding code to the transactions subsystem. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2222) Rename TXFramework -> Compensations

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2222?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-2222: ------------------------------------- For discussion: https://community.jboss.org/message/881063#881063 > Rename TXFramework -> Compensations > ----------------------------------- > > Key: JBTM-2222 > URL: https://issues.jboss.org/browse/JBTM-2222 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.3 > > > TXFramework now just focuses on Compensating transactions. The ACID transaction improvements have been moved into XTS and REST components. Therefore, we should drop the TXFramework name in favour of "Compensations" or "Compensating Transactions". -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2223) Fix Compensations package name to allow for other APIs

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2223?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-2223: ------------------------------------- For discussion: https://community.jboss.org/message/881063#881063 > Fix Compensations package name to allow for other APIs > ------------------------------------------------------ > > Key: JBTM-2223 > URL: https://issues.jboss.org/browse/JBTM-2223 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.3 > > > To allow for other Compensating Transactions APIs, the CDI one needs to be moved into a CDI specific package: > 'org.jboss.narayana.compensations' -> 'org.jboss.narayana.compensations.cdi' -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2221) Remove old TXFramework API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2221?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-2221: ------------------------------------- For discussion: https://community.jboss.org/message/881063#881063 > Remove old TXFramework API > -------------------------- > > Key: JBTM-2221 > URL: https://issues.jboss.org/browse/JBTM-2221 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.3 > > > This is now replaced by the CDI based Compensations API. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2209) Use Deque for ThreadActionData

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-2209?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-2209: ----------------------------------- Thanks, but that's about as much use to me as a chocolate fireguard! ;) Or giving me a scalar number when I need a vector. What was the test used? How many iterations? We could do this ourselves of course, but it'd be so much simpler if you've already done that work :-) > Use Deque for ThreadActionData > ------------------------------ > > Key: JBTM-2209 > URL: https://issues.jboss.org/browse/JBTM-2209 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Attachments: Test.java > > > Note, there are other usages of java.util.Stack in the code base that could be changed as well -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 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 July 2014