May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1731) Narayana release process doesn't rev all versions in BT quickstarts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1731?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1731: -------------------------------- Description: The following files still contain 5.0.0.M3-SNAPSHOT: ./blacktie/messaging/basic/client.c ./blacktie/xatmi/queues/makefile ./blacktie/test/blacktie-linux.sh ./blacktie/test/blacktie-vc9x32.bat Need to update the $NARAYANA_SRC/scripts/pre-release.sh script to change these. Look for the lines that start "find . -name". was: The following files still contain 5.0.0.M3-SNAPSHOT: ./blacktie/messaging/basic/client.c ./blacktie/xatmi/queues/makefile ./blacktie/test/blacktie-linux.sh ./blacktie/test/blacktie-vc9x32.bat Need to update the pre-release script to change these. > Narayana release process doesn't rev all versions in BT quickstarts > ------------------------------------------------------------------- > > Key: JBTM-1731 > URL: https://issues.jboss.org/browse/JBTM-1731 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Demonstrator, Documentation > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > The following files still contain 5.0.0.M3-SNAPSHOT: > ./blacktie/messaging/basic/client.c > ./blacktie/xatmi/queues/makefile > ./blacktie/test/blacktie-linux.sh > ./blacktie/test/blacktie-vc9x32.bat > Need to update the $NARAYANA_SRC/scripts/pre-release.sh script to change these. Look for the lines that start "find . -name". -- 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-1731) Narayana release process doesn't rev all versions in BT quickstarts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1731?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1731: -------------------------------- Description: The following files still contain 5.0.0.M3-SNAPSHOT: ./blacktie/messaging/basic/client.c ./blacktie/xatmi/queues/makefile ./blacktie/test/blacktie-linux.sh ./blacktie/test/blacktie-vc9x32.bat Need to update the pre-release script to change these. was: The following files still contain 5.0.0.M3-SNAPSHOT: blacktie/messaging/basic/client.c blacktie/xatmi/queues/makefile > Narayana release process doesn't rev all versions in BT quickstarts > ------------------------------------------------------------------- > > Key: JBTM-1731 > URL: https://issues.jboss.org/browse/JBTM-1731 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Demonstrator, Documentation > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M4 > > > The following files still contain 5.0.0.M3-SNAPSHOT: > ./blacktie/messaging/basic/client.c > ./blacktie/xatmi/queues/makefile > ./blacktie/test/blacktie-linux.sh > ./blacktie/test/blacktie-vc9x32.bat > Need to update the pre-release script to change these. -- 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-1731) Narayana release process doesn't rev all versions in BT quickstarts

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1731?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1731: -------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > Narayana release process doesn't rev all versions in BT quickstarts > ------------------------------------------------------------------- > > Key: JBTM-1731 > URL: https://issues.jboss.org/browse/JBTM-1731 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, Demonstrator, Documentation > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > The following files still contain 5.0.0.M3-SNAPSHOT: > ./blacktie/messaging/basic/client.c > ./blacktie/xatmi/queues/makefile > ./blacktie/test/blacktie-linux.sh > ./blacktie/test/blacktie-vc9x32.bat > Need to update the pre-release script to change these. -- 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-1731) Narayana release process doesn't rev all versions in BT quickstarts

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1731: ----------------------------------- Summary: Narayana release process doesn't rev all versions in BT quickstarts Key: JBTM-1731 URL: https://issues.jboss.org/browse/JBTM-1731 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System, Demonstrator, Documentation Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M4 The following files still contain 5.0.0.M3-SNAPSHOT: blacktie/messaging/basic/client.c blacktie/xatmi/queues/makefile -- 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-1730) narayana-dualstack does not test TXF and ArjunaJTA/cdi

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1730: ----------------------------------- Summary: narayana-dualstack does not test TXF and ArjunaJTA/cdi Key: JBTM-1730 URL: https://issues.jboss.org/browse/JBTM-1730 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA, Testing, TXFramework Reporter: Paul Robinson Assignee: Gytis Trikleris Fix For: 5.0.0.M4 Notice these lines of output: {code} The requested profile "arqIPv6" could not be activated because it does not exist. {code} in: http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/108/con... Maybe we could make narayana.sh fail if this problem occurs. Better than it failing silently as it does now. -- 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-1565) Allow callback server to open on a random port and override from the system property

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1565?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1565: ------------------------------------- Hi Crispin, Please can you: 1. Sign our CLA: https://cla.jboss.org/index.seam (choose JBoss Transactions rather than BlackTie) 2. Raise a pull request for your change? This will then run CI over the proposed enhancement and double check it for us I will then merge the PR after it passes :) Thanks, Tom > Allow callback server to open on a random port and override from the system property > ------------------------------------------------------------------------------------ > > Key: JBTM-1565 > URL: https://issues.jboss.org/browse/JBTM-1565 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: BlackTie > Affects Versions: 5.0.0.M2 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.Final > > > currently the client can only use the port defined for <SOCKETSERVER> in the btconfig.xml and multi clients can not run together. > we need to allow callback server to open the random port when <SOCKETSERVER PORT="0"> or a range <SOCKETSERVER "12340-12350"> and they could be overridden by socketserver_port and socketserver_host environment variables. -- 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-1728) Use a global environment variable in CI for version numbers of Narayana and WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1728?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1728: -------------------------------- Summary: Use a global environment variable in CI for version numbers of Narayana and WildFly (was: Use a global environment variable in CI for wildfly version) > Use a global environment variable in CI for version numbers of Narayana and WildFly > ----------------------------------------------------------------------------------- > > Key: JBTM-1728 > URL: https://issues.jboss.org/browse/JBTM-1728 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > We have "8.0.0.Alpha2-SNAPSHOT" scattered over many jobs. This is a pain to change every time we have a new release of Wildfly. > We should use a global env variable instead. See the following for how to do it. Notice that I have already added one for Narayana. > http://172.17.131.2/configure > Call the variable WILDFLY_CURRENT_VERSION and set it to "8.0.0.Alpha2-SNAPSHOT". > Ask paul to update the sanity check job before this is done. This will blacklist the usage of hardcoded wildfly version numbers. It will make it a lot easier to find all the places it is used. -- 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-1729) ArjunaJTA/cdi/pom.xml depends on org.jboss.narayana.jta:jta which is not released to Nexus

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1729: ----------------------------------- Summary: ArjunaJTA/cdi/pom.xml depends on org.jboss.narayana.jta:jta which is not released to Nexus Key: JBTM-1729 URL: https://issues.jboss.org/browse/JBTM-1729 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Build System, JTA Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M4 More details to follow... -- 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-1727) Some REST-AT artefacts are not installed

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1727?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1727: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Some REST-AT artefacts are not installed > ---------------------------------------- > > Key: JBTM-1727 > URL: https://issues.jboss.org/browse/JBTM-1727 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/narayana/TESTS=MAIN,jdk=jd... > {code} > [ERROR] Failed to execute goal on project wildfly-rts: Could not resolve dependencies for project org.wildfly:wildfly-rts:jar:8.0.0.Alpha2-SNAPSHOT: Failed to collect dependencies for [org.jboss.narayana.rts:restat-integration:jar:5.0.0.M4-SNAPSHOT (compile), org.jboss.narayana.rts:restat-api:jar:5.0.0.M4-SNAPSHOT (compile), org.jboss.narayana.rts:restat-util:jar:5.0.0.M4-SNAPSHOT (compile), org.wildfly:wildfly-undertow:jar:8.0.0.Alpha2-SNAPSHOT (compile), org.jboss.resteasy:jaxrs-api:jar:3.0-beta-4 (compile), org.jboss.resteasy:resteasy-jaxrs:jar:3.0-beta-4 (compile), org.jboss.resteasy:resteasy-jaxb-provider:jar:3.0-beta-4 (compile), org.jboss.resteasy:resteasy-jettison-provider:jar:3.0-beta-4 (compile), org.jboss.logging:jboss-logging:jar:3.1.3.GA (compile), org.jboss.logging:jboss-logging-processor:jar:1.1.0.Final (provided), org.wildfly:wildfly-controller:jar:8.0.0.Alpha2-SNAPSHOT (compile), org.wildfly:wildfly-server:jar:8.0.0.Alpha2-SNAPSHOT (compile), org.wildfly:wildfly-subsystem-test:pom:8.0.0.Alpha2-SNAPSHOT (test), org.wildfly:wildfly-build-config:jar:8.0.0.Alpha2-SNAPSHOT (compile)]: Failed to read artifact descriptor for org.jboss.narayana.rts:restat-integration:jar:5.0.0.M4-SNAPSHOT: Failure to find org.jboss.narayana.rts:rest-tx:pom:5.0.0.M4-SNAPSHOT in http://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] > {code} > To reproduce: > {code} > rm -rf ~/.m2/repository/org/jboss/narayana > ./build.sh clean install -Prelease,all > tree rm -rf ~/.m2/repository/org/jboss/narayana > {code} > Observe that artefacts required in above are missing. > To fix, look at XTS/byteman_support/pom.xml for an example of what we do to put the artefacts in the .m2 dir when the release profile is enabled. You need to do two things. replace the release profile and configure the maven-deploy-plugin. The latter ensures that these artefacts are deployed to Nexus when we do a release. -- 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-1565) Allow callback server to open on a random port and override from the system property

by Crispin Boylan (JIRA)

[ https://issues.jboss.org/browse/JBTM-1565?page=com.atlassian.jira.plugin.... ] Crispin Boylan commented on JBTM-1565: -------------------------------------- i've implemented this in my github repo: https://github.com/cris-b/blacktie/commit/a4c2cdaf90fd58cbcf406c5a605b375... > Allow callback server to open on a random port and override from the system property > ------------------------------------------------------------------------------------ > > Key: JBTM-1565 > URL: https://issues.jboss.org/browse/JBTM-1565 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: BlackTie > Affects Versions: 5.0.0.M2 > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.Final > > > currently the client can only use the port defined for <SOCKETSERVER> in the btconfig.xml and multi clients can not run together. > we need to allow callback server to open the random port when <SOCKETSERVER PORT="0"> or a range <SOCKETSERVER "12340-12350"> and they could be overridden by socketserver_port and socketserver_host environment variables. -- 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 May 2013