Re: [infinispan-dev] merging all the github projects back?
On Nov 19, 2013, at 10:23 AM, Dan Berindei <dan.berindei(a)gmail.com> wrote:
On Tue, Nov 19, 2013 at 11:21 AM, Martin Gencur <mgencur(a)redhat.com> wrote:
On 19.11.2013 09:59, Dan Berindei wrote:
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?
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.
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?
I'm pretty sure it wouldn't be a single module…
The parent, X, can be a single module (or maven project), and then it can list the modules
to build, e.g. the current list of Infinispan Server submodules:
<module>versions</module>
<module>jgroups</module>
<module>infinispan</module>
<module>integration</module>
<module>build</module>
<module>management/server-rhq-plugin</module>
Given that Infinispan Server already uses
<groupId>org.infinispan.server</groupId>, it might make sense for X to be
`server`.
Thoughts?
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
galder(a)redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org