Rename "build" directory to "dist" in the AS build
--------------------------------------------------
Key: JBBUILD-586
URL: https://jira.jboss.org/jira/browse/JBBUILD-586
Project: JBoss Build System
Issue Type: Task
Components: Maven Builds
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: Maven Build Support 2010
The directory "build" should be renamed to "dist" in the AS build. Clebert suggested that this would make it more clear for new users.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Investigate making HASingleton failover "stopOldMaster" RPC synchronous
-----------------------------------------------------------------------
Key: JBAS-7999
URL: https://jira.jboss.org/jira/browse/JBAS-7999
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
When a node becomes master, it tells any previous master to stop. That call is async, probably because long ago this was done on a JGroups up thread and making a sync call from that up thread would hang. This is no longer done on an up thread, so investigate adding a config option to allow is call to go synchronous, thus ensuring the old master is fully stopped before new one starts.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Support recovery scenarios
--------------------------
Key: JBAS-7221
URL: https://jira.jboss.org/jira/browse/JBAS-7221
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Jesper Pedersen
Assignee: Emanuel Muckenhuber
Priority: Blocker
Fix For: JBossAS-6.0.0.Alpha1
This is a container task for adding recovery support into the AS build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make the domain.rar demo comply with TAG-16
-------------------------------------------
Key: JBAS-8889
URL: https://issues.jboss.org/browse/JBAS-8889
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make the description demo comply with TAG-16
--------------------------------------------
Key: JBAS-8883
URL: https://issues.jboss.org/browse/JBAS-8883
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make the domain.description demo comply with TAG-16
---------------------------------------------------
Key: JBAS-8885
URL: https://issues.jboss.org/browse/JBAS-8885
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make the domain.configs demo comply with TAG-16
-----------------------------------------------
Key: JBAS-8884
URL: https://issues.jboss.org/browse/JBAS-8884
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make the client.messaging demo comply with TAG-16
-------------------------------------------------
Key: JBAS-8882
URL: https://issues.jboss.org/browse/JBAS-8882
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Make the client.jms demo comply with TAG-16
-------------------------------------------
Key: JBAS-8881
URL: https://issues.jboss.org/browse/JBAS-8881
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Fix For: 7.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Convert demos to comply with TAG-16 requirements
------------------------------------------------
Key: JBAS-8880
URL: https://issues.jboss.org/browse/JBAS-8880
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.0.0.CR1
TAG-16 lists requirements for examples that we ship (spelled out in more detail at https://docspace.corp.redhat.com/docs/DOC-37891).
This is a parent task for converting existing demos in the demos/ module to comply with TAG-16. There will be subtasks for each existing demo.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira