[JBoss JIRA] (JBTM-1755) Spurious warning messages?
by Mark Little (JIRA)
Mark Little created JBTM-1755:
---------------------------------
Summary: 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
[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, 1 month
[JBoss JIRA] (JBTM-1636) Enhance TRACE for getStatus
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1636?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1636:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Enhance TRACE for getStatus
> ---------------------------
>
> Key: JBTM-1636
> URL: https://issues.jboss.org/browse/JBTM-1636
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.17.3
> Reporter: Jesper Pedersen
> Assignee: Tom Jenkinson
> Priority: Minor
> Fix For: 5.0.0.M4
>
>
> The following
> {noformat}
> TRACE [com.arjuna.ats.jta] (MSC service thread 1-14) TransactionImple.getStatus
> {noformat}
> statement would benefit from logging the actual return value sent to the caller
--
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, 1 month
[JBoss JIRA] (JBTM-1691) Auto-merge in narayana.sh is not robust enough
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1691?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1691:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: (was: 4.17.5)
Resolution: Done
> Auto-merge in narayana.sh is not robust enough
> ----------------------------------------------
>
> Key: JBTM-1691
> URL: https://issues.jboss.org/browse/JBTM-1691
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Tom Jenkinson
> Fix For: 5.0.0.M4
>
>
> This can't be auto=merged:
> {code}
> <<<<<<< HEAD
> <version.org.jboss.jbossts.jbossjts>5.0.0.M2</version.org.jboss.jbossts.jbossjts>
> <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration>
> <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts>
> <version.org.jboss.jboss-vfs>3.2.0.Beta1</version.org.jboss.jboss-vfs>
> <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana>
> =======
> <version.org.jboss.jbossts.jbossjts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts>
> <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts-integration>
> <version.org.jboss.jbossts.jbossxts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossxts>
> <version.org.jboss.jboss-vfs>3.1.0.Final</version.org.jboss.jboss-vfs>
> <version.org.jboss.jbossts.narayana>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.narayana>
> >>>>>>> Upgrade Narayana to 5.0.0.M3-SNAPSHOT
> {code}
> Our current strategy will take our version which results in the old version of jboss-vfs being used, which in turn causes a build failure in WildFly.
> Maybe we should remove the auto-merge and replace with a manual intervention when a conflict occurs?
--
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, 1 month
[JBoss JIRA] (JBTM-1742) Tidy up the JTS IDL
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1742?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1742:
-----------------------------------
Yes, just saw the other link. I thought the standard build still built against both ORBs, but apparently not. So it seems that the JDK ORB doesn't support CORBA:Current. I'll fix and build with both ORBs.
> Tidy up the JTS IDL
> -------------------
>
> Key: JBTM-1742
> URL: https://issues.jboss.org/browse/JBTM-1742
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Mark Little
> Fix For: 5.0.0.M4
>
>
> The IDL hasn't been updated for over a decade and has preprocessor directives in there that are probably no longer needed, unless we want to be backwardly compatible for ORBs that are no longer produced.
--
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, 1 month
[JBoss JIRA] (JBTM-1742) Tidy up the JTS IDL
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1742?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson edited comment on JBTM-1742 at 6/6/13 12:48 PM:
--------------------------------------------------------------
I put some comments on JBTM-1746 (which was raised when CI broke). I will "back port" those comments here..
Comment 1:
Note that it is in the JDK orb IDL processing, rather than jacorb.
A default build does not build the JDK orb but CI will which is where this issue was first discovered. You can reproduce this issue by:
./build.sh clean install -f ArjunaJTS/idl/idlj/pom.xml
Comment 2:
The problem seems to be the following bit of the commit which breaks the JDK ORB idl processing:
These statements were removed:
#ifdef ORB_CURRENT_SUPPORT
interface Current : CORBA::Current
#else
interface Current
#endif
And then replaced with just:
interface Current : CORBA::Current
was (Author: tomjenkinson):
I put some comments on JBTM-1746 (which was raised when CI broke). I will "back port" those comments here..
Comment 1:
Note that it is in the JDK orb IDL processing, rather than jacorb.
A default build does not build the JDK orb but CI will which is where this issue was first discovered. You can reproduce this issue by:
./build.sh clean install -f ArjunaJTS/idl/idlj/pom.xml
Comment 2:
The problem seems to be the following bit of the commit which breaks the JDK ORB idl processing:
#ifdef ORB_CURRENT_SUPPORT
interface Current : CORBA::Current
#else
interface Current
#endif
and went to:
interface Current : CORBA::Current
> Tidy up the JTS IDL
> -------------------
>
> Key: JBTM-1742
> URL: https://issues.jboss.org/browse/JBTM-1742
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Mark Little
> Fix For: 5.0.0.M4
>
>
> The IDL hasn't been updated for over a decade and has preprocessor directives in there that are probably no longer needed, unless we want to be backwardly compatible for ORBs that are no longer produced.
--
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, 1 month
[JBoss JIRA] (JBTM-1742) Tidy up the JTS IDL
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1742?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson edited comment on JBTM-1742 at 6/6/13 12:47 PM:
--------------------------------------------------------------
I put some comments on JBTM-1746 (which was raised when CI broke). I will "back port" those comments here..
Comment 1:
Note that it is in the JDK orb IDL processing, rather than jacorb.
A default build does not build the JDK orb but CI will which is where this issue was first discovered. You can reproduce this issue by:
./build.sh clean install -f ArjunaJTS/idl/idlj/pom.xml
Comment 2:
The problem seems to be the following bit of the commit which breaks the JDK ORB idl processing:
#ifdef ORB_CURRENT_SUPPORT
interface Current : CORBA::Current
#else
interface Current
#endif
and went to:
interface Current : CORBA::Current
was (Author: tomjenkinson):
I put some comments on JBTM-1746 (which was raised when CI broke). I will "back port" those comments here..
Comment 1:
Note that it is in the JDK orb IDL processing, rather than jacorb.
A default build does not build the JDK orb but CI will which is where this issue was first discovered. You can reproduce this issue by:
./build.sh clean install -f ArjunaJTS/idl/idlj/pom.xml
Comment 2:
Seems to be this bit of the commit that removed
#ifdef ORB_CURRENT_SUPPORT
interface Current : CORBA::Current
#else
interface Current
#endif
and went to:
interface Current : CORBA::Current
> Tidy up the JTS IDL
> -------------------
>
> Key: JBTM-1742
> URL: https://issues.jboss.org/browse/JBTM-1742
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JTS
> Affects Versions: 5.0.0.M3
> Reporter: Mark Little
> Assignee: Mark Little
> Fix For: 5.0.0.M4
>
>
> The IDL hasn't been updated for over a decade and has preprocessor directives in there that are probably no longer needed, unless we want to be backwardly compatible for ORBs that are no longer produced.
--
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, 1 month