Re: [infinispan-dev] Removing dependencies from parent

Hello, currently even to start a little Lucene/Infinispan demo Maven is adding a huge set of dependencies to classpath, this is scaring off. For example the parent pom is forcing presence for commons-logging and log4j on the compile and test classpath of all Infinispan modules; while looking in the Infinispan logging adapter org.infinispan.util.logging.LogFactory all modules should work even if both logging frameworks are missing, falling back to Java's java.util.logging.Logger. Of course this is not tested, as the current build process is adding all loggers to the classpath. So my proposal is to move out all dependencies in parent pom from <dependencies> to <dependencyManagement>, submodules should explicitly add the test dependencies they really needed; are you ok with me doing this? Alternatively, I'm going to cut the parent relationship from lucene modules to infinispan parent, but will need to duplicate the good part of parent settings.

Regards, Sanne _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev