[JBoss JIRA] (JBTM-1533) Create a pre-release script
by Paul Robinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1533?page=com.atlassian.jira.plugin.... ]
Paul Robinson updated JBTM-1533:
--------------------------------
Fix Version/s: 5.0.0.M3
(was: 5.0.0.M2)
> Create a pre-release script
> ---------------------------
>
> Key: JBTM-1533
> URL: https://issues.jboss.org/browse/JBTM-1533
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Fix For: 4.17.4, 5.0.0.M3
>
>
> To encompass these steps of the Narayana release process:
> {code}
> BRANCH=<4.17|master>
> CURRENT=<Version number of the release (e.g. 5.0.0.M2)>
> NEXT=<Version number of the next release (e.g. 5.0.0.M3)>
>
>
> for REPO in documentation quickstart narayana
> do
>
> git clone git@github.com:jbosstm/$REPO.git
> cd $REPO
> git checkout $BRANCH
>
> find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/$CURRENT-SNAPSHOT/$CURRENT/g"
> git commit -am "Updated to $CURRENT"
> git tag $CURRENT
>
> find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/$CURRENT/$NEXT-SNAPSHOT/g"
> git commit -am "Updated to $NEXT-SNAPSHOT"
> git push origin $BRANCH --tags
> cd ..
>
> done
> {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-1533) Create a pre-release script
by Paul Robinson (JIRA)
Paul Robinson created JBTM-1533:
-----------------------------------
Summary: Create a pre-release script
Key: JBTM-1533
URL: https://issues.jboss.org/browse/JBTM-1533
Project: JBoss Transaction Manager
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Build System
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 4.17.4, 5.0.0.M2
To encompass these steps of the Narayana release process:
{code}
BRANCH=<4.17|master>
CURRENT=<Version number of the release (e.g. 5.0.0.M2)>
NEXT=<Version number of the next release (e.g. 5.0.0.M3)>
for REPO in documentation quickstart narayana
do
git clone git@github.com:jbosstm/$REPO.git
cd $REPO
git checkout $BRANCH
find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/$CURRENT-SNAPSHOT/$CURRENT/g"
git commit -am "Updated to $CURRENT"
git tag $CURRENT
find . -name \*.java -o -name \*.xml -o -name \*.properties -o -name \*.ent -o -name \INSTALL -o -name \README | grep -v ".svn" | grep -v ".git" | grep -v target | grep -v .idea | xargs sed -i "s/$CURRENT/$NEXT-SNAPSHOT/g"
git commit -am "Updated to $NEXT-SNAPSHOT"
git push origin $BRANCH --tags
cd ..
done
{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-1284) Optionally circumvent ThreadAction in ArjunaCore when using concurrent nested transactions
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1284?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-1284.
---------------------------------
Resolution: Rejected
> Optionally circumvent ThreadAction in ArjunaCore when using concurrent nested transactions
> ------------------------------------------------------------------------------------------
>
> Key: JBTM-1284
> URL: https://issues.jboss.org/browse/JBTM-1284
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Transaction Core
> Reporter: Tom Jenkinson
>
> Needs sanity checking
> We can collaborate on the work via linked GitHub branch
> The problem out of the box is when you AtomicAction "begin" - you will link to the ThreadActionData, as you can see in the test I can circumvent that via a different API call start passing in the parent directly.
> You can see there is precedent to manipulate ThreadActionData: ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/AsyncPrepare.java (doing the prepare in multiple threads)
> I think this is feasible, it may need some thread safety via synchronization in the AtomicAction.
> Nested Transactions in core look to be able to support concurrent access except:
> 1. Threading may not work, will need to check and fix
> 2. ThreadActionData imposes a stack
> You can see in my test (linked in the GitHub branch) I am circumventing the stack.
> we already support nested transactions, it should just be not associating them with a thread and making sure they are thread safe when they talk to their parents
--
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