[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-601) Place Messaging artifacts in the repository

[Ovidiu Feodorov (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=comments#action_12344983 ] 
            
Ovidiu Feodorov commented on JBMESSAGING-601:
---------------------------------------------

Have Prabhat modify his TCK setup to use 1.0.1.GA. I've just run the full JMS test set and it passes 100% (minus the tests confirmed broken by Sun). 
The snapshot directory is rendered irrelevant by this.

> Place Messaging artifacts in the repository
> -------------------------------------------
>
>                 Key: JBMESSAGING-601
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-601
>             Project: JBoss Messaging
>          Issue Type: Task
>          Components: Tests and Performance
>            Reporter: Richard Achmatowicz
>         Assigned To: Ovidiu Feodorov
>            Priority: Critical
>             Fix For: 1.2.0.Alpha2
>
>
> In order to test Messaging within the AS testsuite, we need a scoped deployment of Messaging (as Messaging currently uses modified versions of Remoting and other jars). We also want to use release-admin.xml to create the Messaging configuration for the application server. (NOTE: All of this assumes a JMX-based deployment and testing context, as discussed in our recent conversion concerning JMX vs MC based-deployments.)
> I need to get these artifacts (jboss-messagings-coped.sar, release-admin.xml) somehow, for each release of Messaging which is to be tested. This means placing copies in repository.jboss.com. 
> As for the contents of the scoped sar, I need a version which includes the following:
> (i) all the Messaging classes
> (ii) the modified jars for remoting etc. and a service descriptor to turn on scoping
> (iii) service descriptors for deployment of the Messaging MBeans via JMX
> The contents reflect the fact that this sar will be used together with release-admin,xml to create a Messaging configuration which can be used to start the AS with and run integration tests against Messaging.
> This sar need not contain any test-related deployments, as the testsuite can manage those separately.
> Because we may want to test differing versions of Messaging, such a sar (e.g. named jboss-messaging-scoped.sar) and a copy of release-admin.xml should be available for each version in the repository. At present, the repository supports two versions of Messaging: 1.0.1.CR4, and snapshot. 
> I suppose these could be placed in a resources subdirectory on the repository.

-- 
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