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
