[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Setting up JBoss Messaging integration tests

[ovidiu.feodorov@jboss.com]

rachmatowicz at jboss.com wrote : 
  | 1. Making use of release-admin.xml directly makes sense from the point of view of centralizing the code to create configurations. However, at present, we are pulling only pulling in jboss-messaging.jar into testsuite/thirdparty from repository.jboss.com, and don't have direct access to release-admin.xml. We are looking for a way to set up the configuration which makes life easy as well as being well-suited to the existing testsuite organization.
  | 

Ruel may have a say on this. The repository also provides a "resources" directory, that can be used for auxiliary scripts, I reckon. Quote from http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBuild

anonymous wrote : 
  | 
  | Repository File Structure
  | 
  | ...
  | repository.jboss.com\component name\version\lib
  | repository.jboss.com\component name\version\resources
  | ...
  | 
  | resources - contains idl files, properties files, things of that nature
  | 
  | ...
  | 

rachmatowicz at jboss.com wrote : 
  | 2. The JBAS build and testsuite makes use of a number of names for directories relating to JMS and the existing JBossMQ implementation:
  | trunk/messaging
  | trunk/testsuite/src/main/jms
  | trunk/testsuite/src/main/jmsra
  | trunk/testsuite/src/main/jbossmq
  | trunk/tetstsuite/src/resources/messaging
  | trunk/testsuite/src/resources/jbossmq
  | 
  | 

"trunk/messaging"  is  a wrong name for JBossMQ related stuff to start with, I would change it to "jbossmq" everywhere it shows up in the source tree. Now with SVN is easy. This leaves messaging for us. As Tim said, messaging5 is bad.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968448#3968448

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968448