activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clebert Suconic <clebert.suco...@gmail.com>
Subject Re: JUnit Rule for Embedded Brokers
Date Tue, 22 Dec 2015 20:47:58 GMT
If u want to bootstrap a tooling project Its fine with git access etc.  

But maybe it would be easier as a folder in one of the projects. 


Sent from my iPhone

> On Dec 22, 2015, at 3:14 PM, Christopher Shannon <christopher.l.shannon@gmail.com>
wrote:
> 
> It may need to go into a new subproject (as you pointed out, maybe under
> tooling).  While it could also just go into the activemqunit-l
> project, there are unit tests in almost every sub project and it would be
> nice if the JUnit Rule could be used in any of these projects.  So, we'd
> probably need to put it into a new tooling sub project and create a test
> dependency for it.
> 
> 
> 
> On Tue, Dec 22, 2015 at 2:49 PM, Quinn Stevenson <
> quinn@pronoia-solutions.com> wrote:
> 
>> Thank You for the information.  I found the subproject on the ActiveMQ
>> site, and I will be sure to get familiar with this.
>> 
>> Since my needs are around JMS, I’ll work on a JUnit Rule for the Artemis
>> EmbeddedJMS.
>> 
>> Any suggestions on where to put the JUnit Rule for ActiveMQ 5.x in the
>> source tree?
>> 
>>>> On Dec 22, 2015, at 12:40 PM, Clebert Suconic <clebert.suconic@gmail.com>
>>> wrote:
>>> 
>>> On Tue, Dec 22, 2015 at 2:25 PM, Quinn Stevenson
>>> <quinn@pronoia-solutions.com> wrote:
>>>> Please forgive my ignorance here - but is Artemis the next major
>> version of ActiveMQ?  Or is it something else?
>>> 
>>> I would prefer to say It's a sub project of ActiveMQ. A different
>>> broker. We have been doing quite a lot of new development there.
>>> If you look at the history it was a donation of hornetq to apache as a
>>> sub project of activemq.
>> 
>> 

Mime
View raw message