RE: MORE RANTS. was RE: [JBoss-dev] creating jboss thirdparty directory

2005-05-13 Thread Adrian Brock
On Fri, 2005-05-13 at 00:59, Scott M Stark wrote: The jbossas module I have been talking about is a testcase for validating the breakout of the current jboss-head to validate use of the repository. I thought that is what this module was for and had no other uses. So let's clarify its current

[JBoss-dev] how to test micro container

2005-05-13 Thread Alexey Loubyansky
Adrian, how do you run micro container tests? I am especially interested in XML related ones. Thanks, alex --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle

Re: MORE RANTS. was RE: [JBoss-dev] creating jboss thirdparty directory

2005-05-13 Thread Tom Elrod
Scott M Stark wrote: ... The only thing that has been done as far as I know if removal of remoting from jboss-head to introduce the binary. Correct. I did two things. 1. Added remoting binary and changed the current builds to use the library instead of the module. 2. Added new integration

RE: MORE RANTS. was RE: [JBoss-dev] creating jboss thirdpartydirectory

2005-05-13 Thread Scott M Stark
So you are arguing that there should be seperate a source tree for a given project, and seperate soruce trees for any integration which I am in agreement with. What is not clear is where the source lives. It could be a seperate cvs module from either the integrator and integratee, or it could be

RE: MORE RANTS. was RE: [JBoss-dev] creating jboss thirdpartydirectory

2005-05-13 Thread Adrian Brock
On Fri, 2005-05-13 at 11:53, Scott M Stark wrote: So you are arguing that there should be seperate a source tree for a given project, and seperate soruce trees for any integration which I am in agreement with. What is not clear is where the source lives. It could be a seperate cvs module from