June 2013 - jbossts-issues - Jboss List Archives

[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: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Fix backported to 4.17 branch and passed git pull request > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1755) Spurious warning messages?

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1755?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1755: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/334 > Spurious warning messages? > -------------------------- > > Key: JBTM-1755 > URL: https://issues.jboss.org/browse/JBTM-1755 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M4 > > > [WARNING] The following patterns were never triggered in this artifact inclusion filter: > o 'org.jboss.narayana.jts:narayana-jts-idlj' > [WARNING] The following patterns were never triggered in this artifact exclusion filter: > o '*:javadoc' > o '**' > [WARNING] The following patterns were never triggered in this artifact inclusion filter: > o 'org.jboss.narayana.arjunacore:arjunacore-services' -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1754) Make project names consistent in poms

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1754: ------------------------------------- Hi Paul, I have merged this into master (EAP 6.2), if you need the same feature for EAP 6.1.x you will have to create a different pull request on 4.17 branch as that version is called JBossTS rather than Narayana so the commit can't just be cherry-picked unfortunately. Thanks for the contribution, Tom > Make project names consistent in poms > ------------------------------------- > > Key: JBTM-1754 > URL: https://issues.jboss.org/browse/JBTM-1754 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 5.0.0.M4 > > > The project names used in the build are not consistent which makes it difficult for someone unfamiliar with the project to debug build issues. > Some examples are provided: > ||Dir Name||Artifact ID||Project Name||Proposed Name|| > |/ArjunaJTA|narayana-jta-all|JBoss JTA everything|Narayana: ArjunaJTA| > |/ArjunaJTS/narayana-jts-idlj|narayana-jts-idlj|JBossJTS packaged module with idlj stubs|Narayana: ArjunaJTS idlj| > |/ArjunaJTS/orbportability|orbportability|JBossJTS orb portability|Narayana: ArjunaJTS orbportability| > The project names can be changed without disrupting the way the build works, so these should be changed to match the dir and artifactId as much as possible. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) remove findbugs profile from main build: was disable some plugins

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1672: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Partially Completed Note the comment, please raise separate issues for each plugin > remove findbugs profile from main build: was disable some plugins > ----------------------------------------------------------------- > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > 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 > Fix For: 4.17.5, 5.0.0.M4 > > > In EAP6 environment the dependencies of are not met: > {code} > * findbugs-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1754) Make project names consistent in poms

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1754: -------------------------------- Fix Version/s: 4.17.5 > Make project names consistent in poms > ------------------------------------- > > Key: JBTM-1754 > URL: https://issues.jboss.org/browse/JBTM-1754 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 4.17.5 > > > The project names used in the build are not consistent which makes it difficult for someone unfamiliar with the project to debug build issues. > Some examples are provided: > ||Dir Name||Artifact ID||Project Name||Proposed Name|| > |/ArjunaJTA|narayana-jta-all|JBoss JTA everything|Narayana: ArjunaJTA| > |/ArjunaJTS/narayana-jts-idlj|narayana-jts-idlj|JBossJTS packaged module with idlj stubs|Narayana: ArjunaJTS idlj| > |/ArjunaJTS/orbportability|orbportability|JBossJTS orb portability|Narayana: ArjunaJTS orbportability| > The project names can be changed without disrupting the way the build works, so these should be changed to match the dir and artifactId as much as possible. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1754) Make project names consistent in poms

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1754?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1754: -------------------------------- Fix Version/s: 5.0.0.M4 (was: 4.17.5) > Make project names consistent in poms > ------------------------------------- > > Key: JBTM-1754 > URL: https://issues.jboss.org/browse/JBTM-1754 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 5.0.0.M4 > > > The project names used in the build are not consistent which makes it difficult for someone unfamiliar with the project to debug build issues. > Some examples are provided: > ||Dir Name||Artifact ID||Project Name||Proposed Name|| > |/ArjunaJTA|narayana-jta-all|JBoss JTA everything|Narayana: ArjunaJTA| > |/ArjunaJTS/narayana-jts-idlj|narayana-jts-idlj|JBossJTS packaged module with idlj stubs|Narayana: ArjunaJTS idlj| > |/ArjunaJTS/orbportability|orbportability|JBossJTS orb portability|Narayana: ArjunaJTS orbportability| > The project names can be changed without disrupting the way the build works, so these should be changed to match the dir and artifactId as much as possible. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) remove findbugs profile from main build: was disable some plugins

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1672: -------------------------------- Description: In EAP6 environment the dependencies of are not met: {code} * findbugs-maven-plugin {code} We need to exclude them from eap6 profile. was: In EAP6 environment the dependencies of these plugins are not met: {code} * findbugs-maven-plugin * maven-surefire-plugin * build-helper-maven-plugin * emma-maven-plugin {code} We need to exclude them from eap6 profile. > remove findbugs profile from main build: was disable some plugins > ----------------------------------------------------------------- > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > 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 > Fix For: 4.17.5, 5.0.0.M4 > > > In EAP6 environment the dependencies of are not met: > {code} > * findbugs-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) disable multiple plugins from eap6 profile

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1672: -------------------------------- Fix Version/s: 4.17.5 5.0.0.M4 > disable multiple plugins from eap6 profile > ------------------------------------------ > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > 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 > Fix For: 4.17.5, 5.0.0.M4 > > > In EAP6 environment the dependencies of these plugins are not met: > {code} > * findbugs-maven-plugin > * maven-surefire-plugin > * build-helper-maven-plugin > * emma-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1672) remove findbugs profile from main build: was disable some plugins

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1672?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1672: -------------------------------- Summary: remove findbugs profile from main build: was disable some plugins (was: disable multiple plugins from eap6 profile) > remove findbugs profile from main build: was disable some plugins > ----------------------------------------------------------------- > > Key: JBTM-1672 > URL: https://issues.jboss.org/browse/JBTM-1672 > 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 > Fix For: 4.17.5, 5.0.0.M4 > > > In EAP6 environment the dependencies of these plugins are not met: > {code} > * findbugs-maven-plugin > * maven-surefire-plugin > * build-helper-maven-plugin > * emma-maven-plugin > {code} > We need to exclude them from eap6 profile. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1664) Create a profile that contains the components needed by EAP6

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1664?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1664: -------------------------------- Fix Version/s: 4.17.5 5.0.0.M4 > Create a profile that contains the components needed by EAP6 > ------------------------------------------------------------ > > Key: JBTM-1664 > URL: https://issues.jboss.org/browse/JBTM-1664 > 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 > Fix For: 4.17.5, 5.0.0.M4 > > > Currently EAP6 need these components: > {code} > jbossts-arjuna > jbossts-arjunacore-services > jbossts-arjunacore > jbossts-bridge > jbossts-common > jbossts-idlj-idl > jbossts-jacorb-idl > jbossts-jbossjts-idlj > jbossts-jbossjts-integration > jbossts-jbossjts-jacorb > jbossts-jbosstxbridge > jbossts-jbossxts > jbossts-jtax > jbossts-jts > jbossts-narayana-jta > jbossts-orbportability > jbossts-recovery > jbossts-restat-api > jbossts-restat-util > jbossts-restat-web > jbossts-txframework > jbossts-txoj > jbossts-ws-c11 > jbossts-ws-t11 > jbossts-wsas > jbossts-wscf11 > jbossts-wstx11 > {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, 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 June 2013