You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by André Santi Oliveira <as...@gmail.com> on 2011/05/05 06:19:19 UTC

Collaborate with ActiveMQ project

Hi,


I'm trying to collaborate with ActiveMQ project; then I've read the section
"Developers > Building", I've configured my Eclipse environment with
ActiveMQ project, but now I need some tips how to be productive. For
example, if a change some code in activemq-web-console project, should I
execute mvn to recompile the code, after that start ActiveMQ and finally to
see the changes, or there is a more productive way to do that ?



Thanks,

André de Santi Oliveira

Re: Collaborate with ActiveMQ project

Posted by Johan Edstrom <se...@gmail.com>.
I'd suggest you write tests, fix things, write a few more tests, get the asserts correct, then you 
build, deploy and verify?

AMQ is no different from any other large project, yeah, it'll take a while to get used to all that code, but by reading 
the tests, use-case-tests and bug fix tests you do get a good view into how things are expected to work?

Cheers!

On May 4, 2011, at 10:19 PM, André Santi Oliveira wrote:

> Hi,
> 
> 
> I'm trying to collaborate with ActiveMQ project; then I've read the section
> "Developers > Building", I've configured my Eclipse environment with
> ActiveMQ project, but now I need some tips how to be productive. For
> example, if a change some code in activemq-web-console project, should I
> execute mvn to recompile the code, after that start ActiveMQ and finally to
> see the changes, or there is a more productive way to do that ?
> 
> 
> 
> Thanks,
> 
> André de Santi Oliveira


Re: Collaborate with ActiveMQ project

Posted by Dejan Bosanac <de...@nighttale.net>.
Unit tests should be fine for starters. Especially as there's no much of
those for the web console. You can always start by looking at existing test
pool.

Regards
-- 
Dejan Bosanac - http://twitter.com/dejanb
-----------------
The experts in open source integration and messaging - http://fusesource.com
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Jun 7, 2011 at 12:04 AM, André Santi Oliveira
<as...@gmail.com>wrote:

> Hi,
>
> Do you think it's useful to create unit tests with mock or it's better to
> create just integration tests ?
> I'm creating tests to activemq-web-console project, but it's harder (at the
> beginning) to create integration tests instead of unit tests !
>
>
> Regards,
> André
>
>
> On Thu, May 5, 2011 at 8:01 AM, André Santi Oliveira <asobrasil@gmail.com
> >wrote:
>
> > OK! Thank you guys!
> >
> > I totally agree with you about tests then I'll start doing it
> > as contribution.
> >
> > Regards,
> > André
> >
> >
> > On Thu, May 5, 2011 at 5:50 AM, Gary Tully <ga...@gmail.com> wrote:
> >
> >> Great news, welcome on board.
> >>
> >> For quick round tripping the mvn jetty:run plugin is a great help:
> >>
> >>  > cd activemq-web-console/
> >>  > mvn jetty:run
> >> > curl http://localhost:8080  or whatever in a browser
> >>
> >> There is also a little boot strap class Main.java in the test
> >> directory that does the same thing from main() but it may need some
> >> tweeks.
> >>
> >> I strongly concur with Johan, tests are king, to both validate and
> >> protect changes into the future.
> >> The web-console project could do with some good basic test
> >> infrastructure, it would be a very welcome contribution.
> >>
> >> On 5 May 2011 05:19, André Santi Oliveira <as...@gmail.com> wrote:
> >> > Hi,
> >> >
> >> >
> >> > I'm trying to collaborate with ActiveMQ project; then I've read the
> >> section
> >> > "Developers > Building", I've configured my Eclipse environment with
> >> > ActiveMQ project, but now I need some tips how to be productive. For
> >> > example, if a change some code in activemq-web-console project, should
> I
> >> > execute mvn to recompile the code, after that start ActiveMQ and
> finally
> >> to
> >> > see the changes, or there is a more productive way to do that ?
> >> >
> >> >
> >> >
> >> > Thanks,
> >> >
> >> > André de Santi Oliveira
> >> >
> >>
> >>
> >>
> >> --
> >> http://blog.garytully.com
> >> http://fusesource.com
> >>
> >
> >
>

Re: Collaborate with ActiveMQ project

Posted by André Santi Oliveira <as...@gmail.com>.
Hi,

Do you think it's useful to create unit tests with mock or it's better to
create just integration tests ?
I'm creating tests to activemq-web-console project, but it's harder (at the
beginning) to create integration tests instead of unit tests !


Regards,
André


On Thu, May 5, 2011 at 8:01 AM, André Santi Oliveira <as...@gmail.com>wrote:

> OK! Thank you guys!
>
> I totally agree with you about tests then I'll start doing it
> as contribution.
>
> Regards,
> André
>
>
> On Thu, May 5, 2011 at 5:50 AM, Gary Tully <ga...@gmail.com> wrote:
>
>> Great news, welcome on board.
>>
>> For quick round tripping the mvn jetty:run plugin is a great help:
>>
>>  > cd activemq-web-console/
>>  > mvn jetty:run
>> > curl http://localhost:8080  or whatever in a browser
>>
>> There is also a little boot strap class Main.java in the test
>> directory that does the same thing from main() but it may need some
>> tweeks.
>>
>> I strongly concur with Johan, tests are king, to both validate and
>> protect changes into the future.
>> The web-console project could do with some good basic test
>> infrastructure, it would be a very welcome contribution.
>>
>> On 5 May 2011 05:19, André Santi Oliveira <as...@gmail.com> wrote:
>> > Hi,
>> >
>> >
>> > I'm trying to collaborate with ActiveMQ project; then I've read the
>> section
>> > "Developers > Building", I've configured my Eclipse environment with
>> > ActiveMQ project, but now I need some tips how to be productive. For
>> > example, if a change some code in activemq-web-console project, should I
>> > execute mvn to recompile the code, after that start ActiveMQ and finally
>> to
>> > see the changes, or there is a more productive way to do that ?
>> >
>> >
>> >
>> > Thanks,
>> >
>> > André de Santi Oliveira
>> >
>>
>>
>>
>> --
>> http://blog.garytully.com
>> http://fusesource.com
>>
>
>

Re: Collaborate with ActiveMQ project

Posted by André Santi Oliveira <as...@gmail.com>.
OK! Thank you guys!

I totally agree with you about tests then I'll start doing it
as contribution.

Regards,
André


On Thu, May 5, 2011 at 5:50 AM, Gary Tully <ga...@gmail.com> wrote:

> Great news, welcome on board.
>
> For quick round tripping the mvn jetty:run plugin is a great help:
>
>  > cd activemq-web-console/
>  > mvn jetty:run
> > curl http://localhost:8080  or whatever in a browser
>
> There is also a little boot strap class Main.java in the test
> directory that does the same thing from main() but it may need some
> tweeks.
>
> I strongly concur with Johan, tests are king, to both validate and
> protect changes into the future.
> The web-console project could do with some good basic test
> infrastructure, it would be a very welcome contribution.
>
> On 5 May 2011 05:19, André Santi Oliveira <as...@gmail.com> wrote:
> > Hi,
> >
> >
> > I'm trying to collaborate with ActiveMQ project; then I've read the
> section
> > "Developers > Building", I've configured my Eclipse environment with
> > ActiveMQ project, but now I need some tips how to be productive. For
> > example, if a change some code in activemq-web-console project, should I
> > execute mvn to recompile the code, after that start ActiveMQ and finally
> to
> > see the changes, or there is a more productive way to do that ?
> >
> >
> >
> > Thanks,
> >
> > André de Santi Oliveira
> >
>
>
>
> --
> http://blog.garytully.com
> http://fusesource.com
>

Re: Collaborate with ActiveMQ project

Posted by Gary Tully <ga...@gmail.com>.
Great news, welcome on board.

For quick round tripping the mvn jetty:run plugin is a great help:

 > cd activemq-web-console/
 > mvn jetty:run
> curl http://localhost:8080  or whatever in a browser

There is also a little boot strap class Main.java in the test
directory that does the same thing from main() but it may need some
tweeks.

I strongly concur with Johan, tests are king, to both validate and
protect changes into the future.
The web-console project could do with some good basic test
infrastructure, it would be a very welcome contribution.

On 5 May 2011 05:19, André Santi Oliveira <as...@gmail.com> wrote:
> Hi,
>
>
> I'm trying to collaborate with ActiveMQ project; then I've read the section
> "Developers > Building", I've configured my Eclipse environment with
> ActiveMQ project, but now I need some tips how to be productive. For
> example, if a change some code in activemq-web-console project, should I
> execute mvn to recompile the code, after that start ActiveMQ and finally to
> see the changes, or there is a more productive way to do that ?
>
>
>
> Thanks,
>
> André de Santi Oliveira
>



-- 
http://blog.garytully.com
http://fusesource.com