Hi, Myles:<div><br></div><div>What Java dev environment do you normall work with? �With IntelliJ IDEA it's pretty easy to point the IDE at the src and test directories and add the (very few) JAR dependencies...</div><div>
<br></div><div>The build itself, and running tests, is easily accomplished with Ant (although some of them require you to separately start up a RabbitMQ broker, running locally).</div><div><br></div><div>Best regards,</div>
<div>Jerry<br><br><div class="gmail_quote">On Mon, Nov 12, 2012 at 11:26 AM, Myles McDonnell <span dir="ltr"><<a href="mailto:mcdonnell.myles@googlemail.com" target="_blank">mcdonnell.myles@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Jerry<div><br></div><div>Thank you for your reply to my recent post WRT the above on the Rabbit list. �I didn't explain myself very well, I'm actually looking for some guidance for setting up a dev. env to work on the java client, not build an app that references the java client. �The reason being that I want to implement and contribute a .NET version of the QueuingConsumerCoDel (as referenced here�<a href="http://www.rabbitmq.com/blog/2012/05/11/some-queuing-theory-throughput-latency-and-bandwidth/" target="_blank">http://www.rabbitmq.com/blog/2012/05/11/some-queuing-theory-throughput-latency-and-bandwidth/</a>� and �<a href="https://gist.github.com/2658712" target="_blank">https://gist.github.com/2658712</a>) �and in order to do that I need to understand the internals of the java client.</div>
<div><br></div><div>Any advice much appreciated.</div><div><br></div><div>Kind Regards</div><span class="HOEnZb"><font color="#888888"><div>Myles</div>
</font></span></blockquote></div><br></div>