[
http://jira.jboss.com/jira/browse/JBMESSAGING-150?page=all ]
Ovidiu Feodorov updated JBMESSAGING-150:
----------------------------------------
Description:
Modify j2eetck-mods so when Vendor Implementation config is built, it will include by
default Messaging, and not MQ. Testing Messaging shouldn't require any other
additional steps.
See
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of
affairs.
All TCK-related Messaging configuration files and build scripts are in
https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to
j2eetck-mods.
was:
Modify j2eetck-mods so when Vendor Implementation config is built, it will include by
default Messaging, and not MQ. Testing Messaging shouldn't require any other
additional steps.
See
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of
affairs.
TCK sould test Messaging, and not JBossMQ, by default
-----------------------------------------------------
Key: JBMESSAGING-150
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-150
Project: JBoss Messaging
Issue Type: Sub-task
Components: Tests and Performance
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Minor
Fix For: 1.2.1
Modify j2eetck-mods so when Vendor Implementation config is built, it will include by
default Messaging, and not MQ. Testing Messaging shouldn't require any other
additional steps.
See
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingTCK for the current state of
affairs.
All TCK-related Messaging configuration files and build scripts are in
https://svn.jboss.org/repos/messaging/trunk/src/cts/. They probably should be moved to
j2eetck-mods.
--
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