[JBoss JIRA] (JBTM-1538) Build jboss-as 8.0.0.alpha1 failed with "compile has transitive dependencies"
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1538?page=com.atlassian.jira.plugin.... ]
Paul Robinson resolved JBTM-1538.
---------------------------------
Resolution: Done
> Build jboss-as 8.0.0.alpha1 failed with "compile has transitive dependencies"
> -----------------------------------------------------------------------------
>
> Key: JBTM-1538
> URL: https://issues.jboss.org/browse/JBTM-1538
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Amos Feng
> Assignee: Paul Robinson
> Priority: Critical
> Fix For: 5.0.0.M3
>
>
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Build 8.0.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jboss-as-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-bad-dependencies) @ jboss-as-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-java-version) @ jboss-as-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (enforce-maven-version) @ jboss-as-build ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.2:enforce (ban-transitive-deps) @ jboss-as-build ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message:
> org.jboss.as:jboss-as-build:pom:8.0.0.Alpha1-SNAPSHOT
> org.jboss.narayana.txframework:txframework:jar:5.0.0.M3-SNAPSHOT:compile has transitive dependencies:
> junit:junit:jar:4.11:test
> org.hamcrest:hamcrest-core:jar:1.3:test
> org.jboss.arquillian.junit:arquillian-junit-container:jar:1.0.0.Final:compile
> org.jboss.arquillian.junit:arquillian-junit-core:jar:1.0.0.Final:compile
> org.jboss.arquillian.test:arquillian-test-api:jar:1.0.0.Final:compile
> org.jboss.arquillian.core:arquillian-core-api:jar:1.0.0.Final:compile
> org.jboss.arquillian.test:arquillian-test-spi:jar:1.0.0.Final:compile
> org.jboss.arquillian.core:arquillian-core-spi:jar:1.0.0.Final:compile
> org.jboss.arquillian.container:arquillian-container-test-api:jar:1.0.0.Final:compile
> org.jboss.arquillian.container:arquillian-container-test-spi:jar:1.0.0.Final:compile
> org.jboss.arquillian.container:arquillian-container-spi:jar:1.0.0.Final:compile
> org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-api-base:jar:2.0.0-alpha-2:compile
> org.jboss.arquillian.core:arquillian-core-impl-base:jar:1.0.0.Final:compile
> org.jboss.arquillian.test:arquillian-test-impl-base:jar:1.0.0.Final:compile
> org.jboss.arquillian.container:arquillian-container-impl-base:jar:1.0.0.Final:compile
> org.jboss.arquillian.config:arquillian-config-api:jar:1.0.0.Final:compile
> org.jboss.arquillian.config:arquillian-config-impl-base:jar:1.0.0.Final:compile
> org.jboss.shrinkwrap.descriptors:shrinkwrap-descriptors-spi:jar:2.0.0-alpha-2:compile
> org.jboss.arquillian.container:arquillian-container-test-impl-base:jar:1.0.0.Final:compile
> org.jboss.narayana.rts:restat-util:jar:5.0.0.M3-SNAPSHOT:compile
> org.jboss.narayana.jts:narayana-jts-jacorb:jar:5.0.0.M3-SNAPSHOT:compile has transitive dependencies:
> org.jboss.byteman:byteman:jar:2.0.1:test
> org.jboss.byteman:byteman-submit:jar:2.0.1:test
> org.hornetq:hornetq-core:jar:2.2.13.Final:compile
> jfree:jfreechart:jar:1.0.9:compile
> jfree:jcommon:jar:1.0.12:compile
> tanukisoft:wrapper:jar:3.2.3:compile
> org.jboss.narayana:jbosstxbridge:jar:5.0.0.M3-SNAPSHOT:compile has transitive dependencies:
> org.jboss.narayana.xts:ws-c11:jar:5.0.0.M3-SNAPSHOT:compile
> org.jboss.narayana.xts:ws-c11:jar:api:5.0.0.M3-SNAPSHOT:compile
> org.jboss.narayana.jta:narayana-jta:jar:5.0.0.M3-SNAPSHOT:compile
> org.jboss.narayana.xts:jbossxts:jar:5.0.0.M3-SNAPSHOT:compile has transitive dependencies:
> org.jboss.narayana.arjunacore:arjunacore:jar:5.0.0.M3-SNAPSHOT:compile
> {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, 8 months
[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?focusedWorklogId=12428909&page=... ]
Gytis Trikleris logged work on JBTM-1479:
-----------------------------------------
Author: Gytis Trikleris
Created on: 14/Mar/13 2:10 PM
Start Date: 14/Mar/13 2:10 PM
Worklog Time Spent: 6 hours
Issue Time Tracking
-------------------
Time Spent: 3 days, 5 hours (was: 2 days, 7 hours)
Worklog Id: (was: 12428909)
> 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: 3 days, 5 hours
> Remaining Estimate: 1 day
>
> 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
11 years, 8 months
[JBoss JIRA] (JBTM-1330) Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Description:
Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
LLR
===
Resource 2 provides Coordinator
Resource1 (xar1::prepare();) // sync 1
Resource2 (ds1::insert(tmLog)
ds1::commit() // sync 2)
Resource 1 (xar1::commit(); // sync 3)
Resource 1 (ds1::delete(tmLog))
ds1::commit() // sync 4 (potentally lazy)
XA
==
Resource 1 (xar1::prepare(); // sync 1)
Resource 2 (xar2::prepare(); // sync 2)
Coordinator (insert(tmLog) // sync 3)
Resource 1 (xar1::commit() // sync 4)
Resource 2 (xar2::commit() // sync 5)
Coordinator (delete(tmLog) // sync 6 (potentally lazy))
was:
Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
LLR
===
xar1::prepare(); // sync 1
ds1::insert(tmLog) ds1::commit() // sync 2
xar1::commit(); // sync 3
(potentally lazily) remove (tmLog) // sync 4
XA
==
xar1::prepare(); // sync 1
xar2::prepare(); // sync 2
tm::log() // sync 3
xar1::commit() // sync 4
xar2::commit() // sync 5
(potentally lazily) remove (tmLog) // sync 6
> Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1330
> URL: https://issues.jboss.org/browse/JBTM-1330
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
> LLR
> ===
> Resource 2 provides Coordinator
> Resource1 (xar1::prepare();) // sync 1
> Resource2 (ds1::insert(tmLog)
> ds1::commit() // sync 2)
> Resource 1 (xar1::commit(); // sync 3)
> Resource 1 (ds1::delete(tmLog))
> ds1::commit() // sync 4 (potentally lazy)
> XA
> ==
> Resource 1 (xar1::prepare(); // sync 1)
> Resource 2 (xar2::prepare(); // sync 2)
> Coordinator (insert(tmLog) // sync 3)
> Resource 1 (xar1::commit() // sync 4)
> Resource 2 (xar2::commit() // sync 5)
> Coordinator (delete(tmLog) // sync 6 (potentally lazy))
--
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, 8 months
[JBoss JIRA] (JBTM-1330) Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Description:
Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
LLR
===
xar1::prepare(); // sync 1
ds1::insert(tmLog) ds1::commit() // sync 2
xar1::commit(); // sync 3
(potentally lazily) remove (tmLog) // sync 4
XA
==
xar1::prepare(); // sync 1
xar2::prepare(); // sync 2
tm::log() // sync 3
xar1::commit() // sync 4
xar2::commit() // sync 5
(potentally lazily) remove (tmLog) // sync 6
was:
Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
LLR
===
xar1::prepare(); // sync 1
ds1::insert(tmLog) ds1::commit() // sync 2
xar1::commit(); // sync 3
lazily remove (tmLog) // sync 4
XA
==
xar1::prepare(); // sync 1
xar2::prepare(); // sync 2
tm::log() // sync 3
xar1::commit() // sync 4
xar2::commit() // sync 5
(potentally lazily) remove (tmLog) // sync 6
> Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1330
> URL: https://issues.jboss.org/browse/JBTM-1330
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
> LLR
> ===
> xar1::prepare(); // sync 1
> ds1::insert(tmLog) ds1::commit() // sync 2
> xar1::commit(); // sync 3
> (potentally lazily) remove (tmLog) // sync 4
> XA
> ==
> xar1::prepare(); // sync 1
> xar2::prepare(); // sync 2
> tm::log() // sync 3
> xar1::commit() // sync 4
> xar2::commit() // sync 5
> (potentally lazily) remove (tmLog) // sync 6
--
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, 8 months
[JBoss JIRA] (JBTM-1330) Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Summary: Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources (was: Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources)
> Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1330
> URL: https://issues.jboss.org/browse/JBTM-1330
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
> LLR
> ===
> xar1::prepare(); // sync 1
> ds1::insert(tmLog) ds1::commit() // sync 2
> xar1::commit(); // sync 3
> lazily remove (tmLog) // sync 4
> XA
> ==
> xar1::prepare(); // sync 1
> xar2::prepare(); // sync 2
> tm::log() // sync 3
> xar1::commit() // sync 4
> xar2::commit() // sync 5
> (potentally lazily) remove (tmLog) // sync 6
--
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, 8 months
[JBoss JIRA] (JBTM-1330) Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1330?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1330:
--------------------------------
Summary: Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources (was: Support Last Logging Resource)
> Extend the transaction boundary of a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTM-1330
> URL: https://issues.jboss.org/browse/JBTM-1330
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.Final
>
>
> Where you multiplex the users application table and the transaction log in the same JDBC local transaction.
> LLR
> ===
> xar1::prepare(); // sync 1
> ds1::insert(tmLog) ds1::commit() // sync 2
> xar1::commit(); // sync 3
> lazily remove (tmLog) // sync 4
> XA
> ==
> xar1::prepare(); // sync 1
> xar2::prepare(); // sync 2
> tm::log() // sync 3
> xar1::commit() // sync 4
> xar2::commit() // sync 5
> (potentally lazily) remove (tmLog) // sync 6
--
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, 8 months