<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 19, 2013 at 11:21 AM, Martin Gencur <span dir="ltr"><<a href="mailto:mgencur@redhat.com" target="_blank">mgencur@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On 19.11.2013 09:59, Dan Berindei wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
BTW, Maven rebuilds every module in the reactor every time you run a build. On my machine, it takes 6 minutes to build everything in the Infinispan reactor. Would you really want to wait 6 minutes every time you want to test something in the server?<br>
</blockquote>
<br></div>
Actually, we often end up doing that cos we first need to build ISPN core and then the server which is dependent on ISPN core. It happens quite often that ISPN server works only with latest version of ISPN core.<br>
<br>
So if I understand it correctly, the ISPN server would be integrated in the main ISPN repository. I guess it would be a specific module which you could build on its own (and also run its tests). This would cover the case when you don't need to build ISPN core in order to run the server. Or did I miss something?<span class=""><font color="#888888"><br>
<br></font></span></blockquote><div><br></div><div>I'm pretty sure it wouldn't be a single module...</div><div><br></div></div></div></div>