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

[Richard Achmatowicz (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-601?page=comments#action_12344984 ] 
            
Richard Achmatowicz commented on JBMESSAGING-601:
-------------------------------------------------

I noticed a build problem when trying to use 1.0.1.GA with the AS build earlier this morning (i.e. I changed the version of Messaging from snapshot to 1.0.1.GA in build-thirdparty.xml). Specifically, in the component-info for Messaging, 1.0.1.GA requires serialization 1.0.2.GA or 1.0.3.GA, but serialization 1.0.1.GA is getting pulled in to the build, and the build is failing. 

What is the approach to resolving these sorts of tangled dependencies (as changing the version of serialization which gets pulled in may upset some other component)? Trial and error? Or should these types of changes only be made with consent of the owner?

Richard



> 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