October 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1288) narayana.sh doesn't tollerate situation where existing JBossAS clone is on 'no branch'

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1288: ----------------------------------- Summary: narayana.sh doesn't tollerate situation where existing JBossAS clone is on 'no branch' Key: JBTM-1288 URL: https://issues.jboss.org/browse/JBTM-1288 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.17.1, 5.0.0.M2 If the previous run needed to resolve a conflict, the branch will be left in a state where the rebase was not completed and thus on "no branch". I think the safest thing to do would be to attempt to "git rebase --abort" before calling "checkout 5_BRANCH". Alternatively, we could finish the rebase, by, doing a "git add" of the change and then a "git rebase --continue", but this may be harder to get right. -- 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

2
6
0 / 0

[JBoss JIRA] (JBTM-1291) narayana.sh is building AS7 without the 5_BRANCH TS commits

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1291: ----------------------------------- Summary: narayana.sh is building AS7 without the 5_BRANCH TS commits Key: JBTM-1291 URL: https://issues.jboss.org/browse/JBTM-1291 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 See workspace in job: http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/19/ Here you will notice that (after logging into beacon) that the git branch of jboss-as is '5_BRANCH', but none of the TS commits have been applied. For example, the JBossTS version in the pom.xml is set to 4.16.6.Final and none of the TXFramework changes are applied. -- 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

2
4
0 / 0

[JBoss JIRA] (JBTM-1290) hudson.sh has incorrect default for NARAYANA_VERSION in master

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1290: ----------------------------------- Summary: hudson.sh has incorrect default for NARAYANA_VERSION in master Key: JBTM-1290 URL: https://issues.jboss.org/browse/JBTM-1290 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 See: https://github.com/jbosstm/narayana/blob/master/scripts/hudson/narayana.sh {code} [ $NARAYANA_VERSION ] || NARAYANA_VERSION="4.17.0.Final-SNAPSHOT" {code} This should be set to 5.0.0.M2-SNAPSHOT. -- 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

2
3
0 / 0

[JBoss JIRA] (JBTM-1112) update narayana.sh to build jboss-as from git:/jbosstm/jboss-as

by Amos Feng (JIRA)

Amos Feng created JBTM-1112: ------------------------------- Summary: update narayana.sh to build jboss-as from git:/jbosstm/jboss-as Key: JBTM-1112 URL: https://issues.jboss.org/browse/JBTM-1112 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 5.0.0.M1 Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.1.Final currently we use jboss-as-7.1.1.Final which will always contain JBossTS 4.16.2. Therefore the tests will always run against 4.16.2 of JBossTS and not the new version of the code that this script intends to test. so it need to build jboss-as. #make sure you have built narayana and have a SNAPSHOT (which you currently are) git clone git://github.com/jbosstm/jboss-as.git git checkout 5_BRANCH (for github master, for backporting you will need to use 4_16_BRANCH) build jboss-as -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-247) Update (if necessary) the new integration layer SPIs

by Mark Little (JIRA)

Update (if necessary) the new integration layer SPIs ---------------------------------------------------- Key: JBTM-247 URL: http://jira.jboss.com/jira/browse/JBTM-247 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: JTA Implementation, JTS Implementation Reporter: Mark Little Assigned To: Jonathan Halliday http://anonsvn.jboss.org/repos/jbossas/projects/integration/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-892) Document the usage of the shipped maven installation in the build instructions

by Tom Jenkinson (JIRA)

Document the usage of the shipped maven installation in the build instructions ------------------------------------------------------------------------------ Key: JBTM-892 URL: https://issues.jboss.org/browse/JBTM-892 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.0.0.M2 Include info such as txmvn -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
12
0 / 0

[JBoss JIRA] (JBTM-1124) jbosstm/jboss-as merge failed from the upstream

by Amos Feng (JIRA)

Amos Feng created JBTM-1124: ------------------------------- Summary: jbosstm/jboss-as merge failed from the upstream Key: JBTM-1124 URL: https://issues.jboss.org/browse/JBTM-1124 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Amos Feng Assignee: Tom Jenkinson Fix For: 5.0.0.M2 the following error when doing 'git pull --rebase upstream master' on jbosstm/jboss-as(BRANCH_5). ... Auto-merging pom.xml Auto-merging jacorb/pom.xml CONFLICT (content): Merge conflict in jacorb/pom.xml Auto-merging build/pom.xml Auto-merging build/build.xml Failed to merge in the changes. Patch failed at 0001 5.0.0.M2-SNAPSHOT version of TS ... jacorb/pom.xm ... <dependency> <<<<<<< HEAD <groupId>org.jboss.as</groupId> <artifactId>jboss-as-network</artifactId> </dependency> <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjts</artifactId> ======= <groupId>org.jboss.narayana.jts</groupId> <artifactId>narayana-jts</artifactId> >>>>>>> 5.0.0.M2-SNAPSHOT version of TS </dependency> see https://github.com/jbossas/jboss-as/commit/d3fb1ce3f1688a654e19c0e56b7f98... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBTM-520) Include distribution information in MANIFEST.MF

by Jesper Pedersen (JIRA)

Include distribution information in MANIFEST.MF ----------------------------------------------- Key: JBTM-520 URL: https://jira.jboss.org/jira/browse/JBTM-520 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6.0 Reporter: Jesper Pedersen Priority: Minor It would be nice if the jar files contain information inside the MANIFEST.MF files - like Implementation-Title Implementation-Vendor Implementation-Vendor-Id Implementation-Version -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
14
0 / 0

[JBoss JIRA] (JBTM-1113) artifacts id different between narayana and jbossts when building jboss-as

by Amos Feng (JIRA)

Amos Feng created JBTM-1113: ------------------------------- Summary: artifacts id different between narayana and jbossts when building jboss-as Key: JBTM-1113 URL: https://issues.jboss.org/browse/JBTM-1113 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Amos Feng Assignee: Tom Jenkinson checkout 5_BRANCH on jboss-as and build fail. It looks like we should change groupId from "org.jboss.jbossts" to "org.jboss.narayana" and different artifact id between them: 1. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjts</artifactId> </dependency> 2. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossxts</artifactId> </dependency> 3. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossxts-api</artifactId> </dependency> 4. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbosstxbridge</artifactId> </dependency> 5. <dependency> <groupId>org.jboss.jbossts</groupId> <artifactId>jbossjts-integration</artifactId> </dependency> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBTM-810) Set the default configuration to use socketless communication betweeen the transaction manager and recovery manager for JTA

by Tom Jenkinson (JIRA)

Set the default configuration to use socketless communication betweeen the transaction manager and recovery manager for JTA --------------------------------------------------------------------------------------------------------------------------- Key: JBTM-810 URL: https://jira.jboss.org/browse/JBTM-810 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JTA Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.15.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

4
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2012