[jboss-jira] [JBoss JIRA] Reopened: (JBAS-4600) Rename JBossMQ variables from jboss-messaging to jboss.messaging-mq.lib and add jboss-messaging into build-thirdparty

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4600?page=all ]

Dimitris Andreadis reopened JBAS-4600:
--------------------------------------

             
I'm ok with the messaging-mq property rename:

-         <path refid="jboss.messaging.classpath"/>
+         <path refid="jboss.messaging-mq.classpath"/> 

But I don't think we need JBM in Branch_4_2, if it's not used there. I'm thinking of possibly reverting those two:

- the inclusion of JBM in build-thirdparty.xml, and the new target in build-distr.xml
- altering conf/login-config.xml and installing messaging users/roles by default, even if it is not used.

We'll discuss this in an email thread.


> Rename JBossMQ variables from jboss-messaging to jboss.messaging-mq.lib and add jboss-messaging into build-thirdparty
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4600
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4600
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.2.1.GA
>            Reporter: Clebert Suconic
>         Assigned To: Clebert Suconic
>             Fix For: JBossAS-4.2.2.GA
>
>
> It's not possible to add jboss-messaging into thirdparty as buildmagic/modules/xml defines it as a variable name called jboss-messaging.

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