[ http://jira.jboss.com/jira/browse/JBMESSAGING-185?page=all ]
Clebert Suconic closed JBMESSAGING-185.
---------------------------------------
Resolution: Done
There is some tidy up to be done by QA on integration.. but those tests are already running.
> Run objectweb JMS tests in top of JBoss Messaging
> -------------------------------------------------
>
> Key: JBMESSAGING-185
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-185
> Project: JBoss Messaging
> Issue Type: Task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.4.0.CR1
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMESSAGING-384?page=all ]
Tim Fox updated JBMESSAGING-384:
--------------------------------
Fix Version/s: Miscellaneous
(was: 1.4.0.CR1)
> Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration
> -------------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-384
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-384
> Project: JBoss Messaging
> Issue Type: Sub-task
> Reporter: Ovidiu Feodorov
> Fix For: Miscellaneous
>
>
> Make sure JBossMQ still works as an alternate JMS provider
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Integration with JBossAS ServiceBinding
---------------------------------------
Key: JBMESSAGING-937
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-937
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.2.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: 1.2.1.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=all ]
Tim Fox closed JBMESSAGING-348.
-------------------------------
Resolution: Done
> Automate test run against all supported databases
> -------------------------------------------------
>
> Key: JBMESSAGING-348
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Fix For: 1.4.0.CR1
>
>
> The test suite should be run continuously against all databases we supply a configuration for.
> Initially this should be:
> Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Align directories on examples.. or document how to configure & run clustered examples
-------------------------------------------------------------------------------------
Key: JBMESSAGING-914
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-914
Project: JBoss Messaging
Issue Type: Sub-task
Reporter: Clebert Suconic
Assigned To: Ovidiu Feodorov
Some examples require the server installed as messaging... and all the clustered examples require the server installed as messaging-node0 and messaging-node1
We should be able to run all examples on clustered config.
So, we should be able to document or configure this better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.jboss.com/jira/browse/JBMESSAGING-383?page=all ]
Tim Fox updated JBMESSAGING-383:
--------------------------------
Fix Version/s: Miscellaneous
(was: 1.4.0.CR1)
> Modify jboss-head build script to include Messaging instead of JBossMQ in the "default" configuration
> -----------------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-383
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-383
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: AS Integration
> Reporter: Ovidiu Feodorov
> Priority: Critical
> Fix For: Miscellaneous
>
>
> Make sure JBossMQ still works as an alternate JMS provider
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira