June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1670) Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1670?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1670: -------------------------------- Summary: Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile (was: Remove jfreechart dependency from EAP6 profile) > Add a community profile to enable none-EAP features: was Remove jfreechart dependency from EAP6 profile > ------------------------------------------------------------------------------------------------------- > > Key: JBTM-1670 > URL: https://issues.jboss.org/browse/JBTM-1670 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > Currently in EAP6 there is no jfreechart library so we need to remove the relative components from JBossTS: > {code} > ArjunaCore/arjuna/pom.xml > pom.xml > {code} > And we need to remove these two classes which depend on jfreechart: > {code} > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfPlugin.java > ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1382: ---------------------------------------- Actually it is working. I am leaving the JIRA as open since I want the fix backported and have updated the Fix Version field to include 4.17.5 > QA build does not archive test group summary files > -------------------------------------------------- > > Key: JBTM-1382 > URL: https://issues.jboss.org/browse/JBTM-1382 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.5, 5.0.0.M2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1382) QA build does not archive test group summary files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1382?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1382: ----------------------------------- Fix Version/s: 4.17.5 5.0.0.M2 (was: 5.0.0.M4) > QA build does not archive test group summary files > -------------------------------------------------- > > Key: JBTM-1382 > URL: https://issues.jboss.org/browse/JBTM-1382 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 4.17.5, 5.0.0.M2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The QA test suite consists of a number of test groups. The build produces a summary file showing the status of each sub test within a group (these are called TEST-<test group>.txt and stored in the qa directory). We currently archive the qa/testoutput directory but it would be useful to also archive these summary text files. Note that we cannot rely on Jenkins to do this for us since the jts remote test group is executed twice (once for each orb) and the files from the first run are overwritten. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1671) disable orson as dependecy

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1671?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1671: -------------------------------- Fix Version/s: (was: 4.17.4) > disable orson as dependecy > -------------------------- > > Key: JBTM-1671 > URL: https://issues.jboss.org/browse/JBTM-1671 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Tom Jenkinson > > EAP6 does not ship orson so we need to exclude it from eap6 profile of jbossts: > {code} > ArjunaCore/arjuna/pom.xml > pom.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1671) disable orson as dependecy

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1671?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1671. --------------------------------- Resolution: Duplicate Issue JBTM-1670 > disable orson as dependecy > -------------------------- > > Key: JBTM-1671 > URL: https://issues.jboss.org/browse/JBTM-1671 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.4 > > > EAP6 does not ship orson so we need to exclude it from eap6 profile of jbossts: > {code} > ArjunaCore/arjuna/pom.xml > pom.xml > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1694) Separate emma into new profile so dependency is not required from maven central

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1694: -------------------------------- Summary: Separate emma into new profile so dependency is not required from maven central (was: Use emma jar from a Maven repo instead of checking into the build) > Separate emma into new profile so dependency is not required from maven central > ------------------------------------------------------------------------------- > > Key: JBTM-1694 > URL: https://issues.jboss.org/browse/JBTM-1694 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > Currently in /pom.xml: > {code} > <systemPath>${emma.jar.location}</systemPath> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1694) Use emma jar from a Maven repo instead of checking into the build

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1694?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1694: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/316 > Use emma jar from a Maven repo instead of checking into the build > ----------------------------------------------------------------- > > Key: JBTM-1694 > URL: https://issues.jboss.org/browse/JBTM-1694 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Weinan Li > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > Currently in /pom.xml: > {code} > <systemPath>${emma.jar.location}</systemPath> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1691) Auto-merge in narayana.sh is not robust enough

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1691?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-1691 at 6/3/13 5:50 AM: ------------------------------------------------------------- OK, so I have disabled the ability to auto merge conflicts, this will mean that after the AS pull is merged we will have to rebase 5_BRANCH with the commit in to rev to the CURRENT_RELEASED_VERSION. See note on https://community.jboss.org/wiki/NarayanaReleaseProcess which says: "Once merged, rebase the jbosstm/jboss-as 5_BRANCH|4_BRANCH branch with the updated wildfly master branch" was (Author: tomjenkinson): OK, so I have disabled the ability to auto merge conflicts, this will mean that after the AS pull is merged we will have to rebase 5_BRANCH with the commit in to rev to the CURRENT_RELEASED_VERSION > Auto-merge in narayana.sh is not robust enough > ---------------------------------------------- > > Key: JBTM-1691 > URL: https://issues.jboss.org/browse/JBTM-1691 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > This can't be auto=merged: > {code} > <<<<<<< HEAD > <version.org.jboss.jbossts.jbossjts>5.0.0.M2</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.2.0.Beta1</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana> > ======= > <version.org.jboss.jbossts.jbossjts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.1.0.Final</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.narayana> > >>>>>>> Upgrade Narayana to 5.0.0.M3-SNAPSHOT > {code} > Our current strategy will take our version which results in the old version of jboss-vfs being used, which in turn causes a build failure in WildFly. > Maybe we should remove the auto-merge and replace with a manual intervention when a conflict occurs? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1691) Auto-merge in narayana.sh is not robust enough

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1691?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1691: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/315 OK, so I have disabled the ability to auto merge conflicts, this will mean that after the AS pull is merged we will have to rebase 5_BRANCH with the commit in to rev to the CURRENT_RELEASED_VERSION > Auto-merge in narayana.sh is not robust enough > ---------------------------------------------- > > Key: JBTM-1691 > URL: https://issues.jboss.org/browse/JBTM-1691 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Fix For: 4.17.5, 5.0.0.M4 > > > This can't be auto=merged: > {code} > <<<<<<< HEAD > <version.org.jboss.jbossts.jbossjts>5.0.0.M2</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.2.0.Beta1</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana> > ======= > <version.org.jboss.jbossts.jbossjts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts> > <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts-integration> > <version.org.jboss.jbossts.jbossxts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossxts> > <version.org.jboss.jboss-vfs>3.1.0.Final</version.org.jboss.jboss-vfs> > <version.org.jboss.jbossts.narayana>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.narayana> > >>>>>>> Upgrade Narayana to 5.0.0.M3-SNAPSHOT > {code} > Our current strategy will take our version which results in the old version of jboss-vfs being used, which in turn causes a build failure in WildFly. > Maybe we should remove the auto-merge and replace with a manual intervention when a conflict occurs? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1673) xatmi build with valgrind failure

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1673?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1673: ------------------------------------- Great work Amos, I will disable valgrind on 64 el5 configuration. > xatmi build with valgrind failure > --------------------------------- > > Key: JBTM-1673 > URL: https://issues.jboss.org/browse/JBTM-1673 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.Final > > > http://172.17.131.2/job/blacktie-linux64-el5/1548/ > http://172.17.131.2/job/blacktie-linux64-el5/1503/ > http://172.17.131.2/job/blacktie-linux64-el5/1492/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 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 June 2013