[JBoss JIRA] (JBTM-1479) Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1479?page=com.atlassian.jira.plugin.... ]
Work on JBTM-1479 stopped by Gytis Trikleris.
> Create a quickstart to show how to use IronJacamar and JBTM inside tomcat
> -------------------------------------------------------------------------
>
> Key: JBTM-1479
> URL: https://issues.jboss.org/browse/JBTM-1479
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Fix For: 5.0.0.M3
>
> Attachments: test-ds.xml, transaction.xml
>
> Original Estimate: 3 days
> Time Spent: 4 days, 1 hour, 30 minutes
> Remaining Estimate: 3 hours, 30 minutes
>
> See JBTM-809 for the algorithm
> You might want to put the startup in the context listener:
> public class MyServletContextListener implements ServletContextListener {
> public void contextInitialized(ServletContextEvent sce) {
> // Initialize RecoveryManager
> // Initialize TransactionManager
> // Initialize IronJacamar
> }
>
> @Override
> public void contextDestroyed(ServletContextEvent sce) {
> // Clean IronJacamar
> // Clean TransactionManager
> // Clean RecoveryManager
> }
> }
> Quickstart application should connect to the database (say PostgreSQL), dummy XA resource and coordinate the transaction. The PostgreSQL data source needs to be accessed via IronJacamar.
--
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
13 years
[JBoss JIRA] (JBTM-1554) Create a job for PR on 5_BRANCH and 4_BRANCH
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1554?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1554:
--------------------------------
Description:
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.
was:
This will allow us to test changes to our AS fork before merging.
We should also come up with a plan for building PR on 5_BRANCH and Narayana together. This is required for situations when we need to make commits to both code basis that are mutually dependent.
> 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: Paul Robinson
> 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
13 years
[JBoss JIRA] (JBTM-1551) Empty '.m2/repository/org/jboss/narayana' prior to running CI
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1551?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1551:
--------------------------------
Original Estimate: 15 minutes (was: 1 hour)
Remaining Estimate: 15 minutes (was: 1 hour)
> Empty '.m2/repository/org/jboss/narayana' prior to running CI
> -------------------------------------------------------------
>
> Key: JBTM-1551
> URL: https://issues.jboss.org/browse/JBTM-1551
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> This ensures that no old artefacts are picked up.
> Need to wait for BT to be merged into Narayana as it relies on Narayana artefacts being present in .m2. A failed Narayana build will result in these artefacts being missing.
--
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
13 years
[JBoss JIRA] (JBTM-1525) Remove version numbers from all but parent pom
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1525?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1525:
--------------------------------
Description:
We have a lot of version numbers scattered throughout our poms. Most of which should be in the root pom. This task is to hunt them all down and move the versions into the root.
I think this finds them:
{code}
grep -r "<version>" **/*/pom.xml
{code}
Not sure if it gets them all.
was:
I think this finds them:
{code}
grep -r "<version>" **/*/pom.xml
{code}
Not sure if it gets them all.
> Remove version numbers from all but parent pom
> ----------------------------------------------
>
> Key: JBTM-1525
> URL: https://issues.jboss.org/browse/JBTM-1525
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M3
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> We have a lot of version numbers scattered throughout our poms. Most of which should be in the root pom. This task is to hunt them all down and move the versions into the root.
> I think this finds them:
> {code}
> grep -r "<version>" **/*/pom.xml
> {code}
> Not sure if it gets them all.
--
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
13 years
[JBoss JIRA] (JBTM-1525) Remove version numbers from all but parent pom
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1525?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1525:
--------------------------------
Description:
I think this finds them:
{code}
grep -r "<version>" **/*/pom.xml
{code}
Not sure if it gets them all.
was:
I think this finds them:
{code}
grep -r "<version>" **/*/pom.xml | wc -l
{code}
Not sure if it gets them all.
> Remove version numbers from all but parent pom
> ----------------------------------------------
>
> Key: JBTM-1525
> URL: https://issues.jboss.org/browse/JBTM-1525
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> I think this finds them:
> {code}
> grep -r "<version>" **/*/pom.xml
> {code}
> Not sure if it gets them all.
--
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
13 years
[JBoss JIRA] (JBTM-1558) Provide an SPI for the AS
by Tom Jenkinson (JIRA)
Tom Jenkinson created JBTM-1558:
-----------------------------------
Summary: Provide an SPI for the AS
Key: JBTM-1558
URL: https://issues.jboss.org/browse/JBTM-1558
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Application Server Integration
Reporter: Tom Jenkinson
Assignee: Tom Jenkinson
Fix For: 5.0.0.M3
We can use jboss-transaction-spi to get started
--
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
13 years
[JBoss JIRA] (JBTM-1525) Remove version numbers from all but parent pom
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1525?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1525:
--------------------------------
Description:
I think this finds them:
{code}
grep -r "<version>" **/*/pom.xml | wc -l
{code}
Not sure if it gets them all.
was:
In particular:
txbridge/pom/xml
> Remove version numbers from all but parent pom
> ----------------------------------------------
>
> Key: JBTM-1525
> URL: https://issues.jboss.org/browse/JBTM-1525
> Project: JBoss Transaction Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.M3
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> I think this finds them:
> {code}
> grep -r "<version>" **/*/pom.xml | wc -l
> {code}
> Not sure if it gets them all.
--
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
13 years