[ http://jira.jboss.com/jira/browse/JBMESSAGING-383?page=all ]
Ovidiu Feodorov updated JBMESSAGING-383:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> 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
> Assigned To: Ovidiu Feodorov
> Priority: Critical
> Fix For: 1.2.1
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-386?page=all ]
Ovidiu Feodorov updated JBMESSAGING-386:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> Isolate JBossMQ-specific tests and make sure they pass
> ------------------------------------------------------
>
> Key: JBMESSAGING-386
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-386
> Project: JBoss Messaging
> Issue Type: Sub-task
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Priority: Critical
> Fix For: 1.2.1
>
>
> Move them inside the JBossMQ project as functional tests
--
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-387?page=all ]
Ovidiu Feodorov updated JBMESSAGING-387:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> Modify the admin console to work with Messaging while keeping JBossMQ compatibility
> -----------------------------------------------------------------------------------
>
> Key: JBMESSAGING-387
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-387
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: AS Integration
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Fix For: 1.2.1
>
>
> JSR77
> Charles
--
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-378?page=all ]
Ovidiu Feodorov updated JBMESSAGING-378:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> Use memory leak detection within the testsuite
> ----------------------------------------------
>
> Key: JBMESSAGING-378
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-378
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Priority: Minor
> Fix For: 1.2.1
>
> Original Estimate: 2 minutes
> Remaining Estimate: 2 minutes
>
> Clebert's stuff.
--
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-116?page=all ]
Ovidiu Feodorov updated JBMESSAGING-116:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> Create a 'messaging' configuration in jboss-head
> ------------------------------------------------
>
> Key: JBMESSAGING-116
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-116
> Project: JBoss Messaging
> Issue Type: Task
> Components: AS Integration
> Affects Versions: 1.0.0 alpha PR2 (clustered)
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Fix For: 1.2.1
>
>
> Update jboss-head/build/build.xml partition-build to create a "messaging" configuration.
--
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-382?page=all ]
Ovidiu Feodorov updated JBMESSAGING-382:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> Make Messaging the default JMS provider for JBoss 5.0
> -----------------------------------------------------
>
> Key: JBMESSAGING-382
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-382
> Project: JBoss Messaging
> Issue Type: Task
> Components: AS Integration
> Reporter: Ovidiu Feodorov
> Priority: Critical
> Fix For: 1.2.1
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
--
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-82?page=all ]
Ovidiu Feodorov updated JBMESSAGING-82:
---------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> CLIENT_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE optimizations
> -----------------------------------------------------
>
> Key: JBMESSAGING-82
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-82
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: JMS Facade
> Reporter: Ovidiu Feodorov
> Assigned To: Tim Fox
> Priority: Minor
> Fix For: 1.2.1
>
> Original Estimate: 2 days
> Remaining Estimate: 2 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-185?page=all ]
Ovidiu Feodorov updated JBMESSAGING-185:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> 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: rajdeep dua
> Fix For: 1.2.1
>
> 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-259?page=all ]
Ovidiu Feodorov updated JBMESSAGING-259:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.0.4)
> Activate compression in marshaller
> ----------------------------------
>
> Key: JBMESSAGING-259
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Tim Fox
> Fix For: 1.2.1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Activate compression in marshaller for messages > x bytes. Make it configurable
--
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