April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?page=com.atlassian.jira.plugin.... ] Work on JBTM-1365 stopped by Gytis Trikleris. > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 2 days, 4 hours > Remaining Estimate: 2 weeks, 2 days, 4 hours > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12428939&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 04/Apr/13 5:24 AM Start Date: 04/Apr/13 5:24 AM Worklog Time Spent: 1 day, 1 hour Issue Time Tracking ------------------- Remaining Estimate: 2 weeks, 2 days, 4 hours (was: 2 weeks, 3 days, 5 hours) Time Spent: 2 days, 4 hours (was: 1 day, 3 hours) Worklog Id: (was: 12428939) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 2 days, 4 hours > Remaining Estimate: 2 weeks, 2 days, 4 hours > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1407: -------------------------------- Priority: Critical (was: Major) > Have a build option that builds JTS only against JacORB or IDLJ, but not both. > ------------------------------------------------------------------------------ > > Key: JBTM-1407 > URL: https://issues.jboss.org/browse/JBTM-1407 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M3 > > Time Spent: 3 days, 1 hour, 51 minutes > Remaining Estimate: 3 days > > This boils down to supporting two new profiles: > ./build.sh -P jts-jacorb > ./build.sh -P jts-idlj -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1554) Create a job for PR on 5_BRANCH and 4_BRANCH

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1554?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1554: -------------------------------- Priority: Critical (was: Major) > Create a job for PR on 5_BRANCH and 4_BRANCH > -------------------------------------------- > > Key: JBTM-1554 > URL: https://issues.jboss.org/browse/JBTM-1554 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.0.M3 > > > This will allow us to test changes to our AS fork before merging. I suggest we run all the tests that AS run on lightning, followed by all the Narayana tests. > We should also come up with a plan for building PR on 4_BRANCH or 5_BRANCH and Narayana together. This is required for situations when we need to make commits to both code basis that are mutually dependent. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1452) Distribution name of 4.17.x is narayana* rather than jbossts*

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1452?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1452: -------------------------------- Priority: Critical (was: Major) > Distribution name of 4.17.x is narayana* rather than jbossts* > ------------------------------------------------------------- > > Key: JBTM-1452 > URL: https://issues.jboss.org/browse/JBTM-1452 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.3 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > See https://www.jboss.org/jbosstm/downloads/4_17_3_Final -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1598: -------------------------------- Priority: Critical (was: Major) > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1598) version tags missed for all the sub-components

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1598?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1598: -------------------------------- Component/s: Build System > version tags missed for all the sub-components > ---------------------------------------------- > > Key: JBTM-1598 > URL: https://issues.jboss.org/browse/JBTM-1598 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Weinan Li > Assignee: Gytis Trikleris > Fix For: 4.17.4, 5.0.0.M3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Hi Tom, the problem I've found is that all the dependencies of its own components are lack of version section. For example: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > </dependency> > </dependencies> > {code} > Should be: > {code} > <dependencies> > <dependency> > <groupId>org.jboss.jbossts</groupId> > <artifactId>common</artifactId> > <version>${project.version}</version> > </dependency> > </dependencies> > {code} > Could you please help to add these tags? Thanks! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1407: -------------------------------- Priority: Major (was: Minor) > Have a build option that builds JTS only against JacORB or IDLJ, but not both. > ------------------------------------------------------------------------------ > > Key: JBTM-1407 > URL: https://issues.jboss.org/browse/JBTM-1407 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, JTS > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Time Spent: 3 days, 1 hour, 51 minutes > Remaining Estimate: 3 days > > This boils down to supporting two new profiles: > ./build.sh -P jts-jacorb > ./build.sh -P jts-idlj -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1599) transactional fileio maven artifact not in nexus

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1599?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1599: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > transactional fileio maven artifact not in nexus > ------------------------------------------------ > > Key: JBTM-1599 > URL: https://issues.jboss.org/browse/JBTM-1599 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 5.0.0.M2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M3 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-865) Make sure REST-AT is covered in docbook

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-865?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-865: ------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > Make sure REST-AT is covered in docbook > --------------------------------------- > > Key: JBTM-865 > URL: https://issues.jboss.org/browse/JBTM-865 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: REST > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > > Include a section on REST-AT in docbook -- 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, 9 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 April 2013