12:45 p.m.
This stems from a discussion Adrian and I had about the maven module
structure for Infinispan and how it could change to be more modular.
/pom.xml <-- parent POM, used to build/test the entire project
/project <- project details such as team and common factors across all
modules (Artifact Id: infinispan-project)
/distribution <-- aggregator POM to build a complete and coherent
distribution (Artifact Id: infinispan-distribution)
/core <-- core code + tests. (Artifact Id: infinispan-core)
/cachestore/* <-- several sub-modules here, for cache stores that have
external dependencies. Such as JDBC, BDBJE, S3 so that external
dependencies can be mapped separately. Typical artifact ids: infinispan-
cachestore-bdbje
/tree <-- for the tree cache API (Artifact Id: infinispan-tree)
/fine-grained <-- for the fine-grained API (Artifact Id: infinispan-fine-
grained)
Any thoughts/comments/suggestions on the above?
Cheers
--
Manik Surtani
Lead, JBoss Cache
http://www.jbosscache.org
manik(a)jboss.org
1:41 p.m.
+1 -Adrian
On 01/04/2009, Manik Surtani <manik(a)jboss.org> wrote:
This stems from a discussion Adrian and I had about the maven module
structure for Infinispan and how it could change to be more modular.
/pom.xml <-- parent POM, used to build/test the entire project
/project <- project details such as team and common factors across all
modules (Artifact Id: infinispan-project)
/distribution <-- aggregator POM to build a complete and coherent
distribution (Artifact Id: infinispan-distribution)
/core <-- core code + tests. (Artifact Id: infinispan-core)
/cachestore/* <-- several sub-modules here, for cache stores that have
external dependencies. Such as JDBC, BDBJE, S3 so that external
dependencies can be mapped separately. Typical artifact ids: infinispan-
cachestore-bdbje
/tree <-- for the tree cache API (Artifact Id: infinispan-tree)
/fine-grained <-- for the fine-grained API (Artifact Id: infinispan-fine-
grained)
Any thoughts/comments/suggestions on the above?
Cheers
--
Manik Surtani
Lead, JBoss Cache
http://www.jbosscache.org
manik(a)jboss.org
--
Sent from my mobile device
2:21 p.m.
Manik Surtani wrote:
This stems from a discussion Adrian and I had about the maven module
structure for Infinispan and how it could change to be more modular.
What's the aim for making Infinispan more modular? Release individual
modules independently? Make it easier for people to select which modules
they need?
Do you expect different people to own different modules?
/pom.xml <-- parent POM, used to build/test the entire project
/project <- project details such as team and common factors across all
modules (Artifact Id: infinispan-project)
/distribution <-- aggregator POM to build a complete and coherent
distribution (Artifact Id: infinispan-distribution)
/core <-- core code + tests. (Artifact Id: infinispan-core)
Shouldn't project/ and distribution/ just live under core/?
/cachestore/* <-- several sub-modules here, for cache stores that have
external dependencies. Such as JDBC, BDBJE, S3 so that external
dependencies can be mapped separately. Typical artifact ids:
infinispan-cachestore-bdbje
So, each sub-module would have pom.xml? Would there also be another
pom.xml at the root of cachestore/?
/tree <-- for the tree cache API (Artifact Id: infinispan-tree)
/fine-grained <-- for the fine-grained API (Artifact Id:
infinispan-fine-grained)
Any thoughts/comments/suggestions on the above?
Having separate modules for tree, fine-grained, cachestores make sense
to me.
Cheers
--
Manik Surtani
Lead, JBoss Cache
http://www.jbosscache.org
manik(a)jboss.org
------------------------------------------------------------------------
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
2:27 p.m.
On 1 Apr 2009, at 13:21, Galder Zamarreno wrote:
Manik Surtani wrote:
> This stems from a discussion Adrian and I had about the maven
> module structure for Infinispan and how it could change to be more
> modular.
What's the aim for making Infinispan more modular? Release individual
modules independently? Make it easier for people to select which
modules they need?
The last one. They will not be released independently, but it helps
consumers control bloat/dependencies. E.g., if you have a maven
project which just uses the core Infinispan API, you would just declare a
dependency on infinispan-core. If you also used a FileCacheStore, you
need not add anything, but if you used a BdbjeCacheStore you would add
a dependency on infinispan-cachestore-bdbje which in turn would pull down
bdbje jars.
Do you expect different people to own different modules?
You mean from a development perspective? Not necessarily, although it
may naturally work out that way for smaller modules.
> /pom.xml <-- parent POM, used to build/test the entire
project
> /project <- project details such as team and common factors across
> all modules (Artifact Id: infinispan-project)
> /distribution <-- aggregator POM to build a complete and coherent
> distribution (Artifact Id: infinispan-distribution)
> /core <-- core code + tests. (Artifact Id: infinispan-core)
Shouldn't project/ and distribution/ just live under core/?
It could, but then you have issues where you may want to build/test
just core versus the entire distribution. There may be sense in
combining project and core though, since project is just a common
parent for all modules.
> /cachestore/* <-- several sub-modules here, for cache stores that
> have external dependencies. Such as JDBC, BDBJE, S3 so that
> external dependencies can be mapped separately. Typical artifact
> ids: infinispan-cachestore-bdbje
So, each sub-module would have pom.xml? Would there also be another
pom.xml at the root of cachestore/?
Maybe not at the root of cachestore. The subdirs are just for
organization and to make it clear that those modules are cachestore
modules.
Cheers
--
Manik Surtani
Lead, JBoss Cache
http://www.jbosscache.org
manik(a)jboss.org
2:35 p.m.
Having project disconnected from core allows us to mandate certain
things, like style and license, across all modules without introducing
other dependencies from core. Dist could be put into core, but would
clutter it a bit. ideally, poms are like classes: one reason to
change. What do you think? Adrian cole
On 01/04/2009, Galder Zamarreno <galder.zamarreno(a)redhat.com> wrote:
Manik Surtani wrote:
> This stems from a discussion Adrian and I had about the maven module
> structure for Infinispan and how it could change to be more modular.
What's the aim for making Infinispan more modular? Release individual
modules independently? Make it easier for people to select which modules
they need?
Do you expect different people to own different modules?
>
> /pom.xml <-- parent POM, used to build/test the entire project
>
> /project <- project details such as team and common factors across all
> modules (Artifact Id: infinispan-project)
>
> /distribution <-- aggregator POM to build a complete and coherent
> distribution (Artifact Id: infinispan-distribution)
>
> /core <-- core code + tests. (Artifact Id: infinispan-core)
Shouldn't project/ and distribution/ just live under core/?
>
> /cachestore/* <-- several sub-modules here, for cache stores that have
> external dependencies. Such as JDBC, BDBJE, S3 so that external
> dependencies can be mapped separately. Typical artifact ids:
> infinispan-cachestore-bdbje
So, each sub-module would have pom.xml? Would there also be another
pom.xml at the root of cachestore/?
>
> /tree <-- for the tree cache API (Artifact Id: infinispan-tree)
> /fine-grained <-- for the fine-grained API (Artifact Id:
> infinispan-fine-grained)
>
> Any thoughts/comments/suggestions on the above?
Having separate modules for tree, fine-grained, cachestores make sense
to me.
> Cheers
>
> --
> Manik Surtani
> Lead, JBoss Cache
> http://www.jbosscache.org
> manik(a)jboss.org
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Sent from my mobile device
5755
days inactive
5755
days old
infinispan-dev@lists.jboss.org
4 comments
3 participants
participants (3)
-
Adrian Cole -
Galder Zamarreno -
Manik Surtani