Hi, they're needed for compiling/running SiteGeneratorTest, which updates the site files:
* jspwiki-war:classes, which contains o.a.w.Release * commons-io and commons-lang, to make use of o.a.c.io.FileUtils and o.a.c.lang.StringUtils respectively * log4j, used in SiteGeneratorTest, and junit to run the test in this file all dependencies are test scoped in this module. Btw, just noticed, could we push junit down to our jspwiki-builder? Most probably it's going to be defined in all the modules.. br, juan pablo On Sun, Jul 14, 2013 at 9:03 PM, Glen Mazza <[email protected]> wrote: > Incidentally, JP, are any of the dependencies in jspwiki-site/pom.xml > used? I don't understand their purpose, as that submodule AFAICT doesn't > generate or do anything but just sit there. > > > Glen > > On 07/12/2013 04:35 PM, Juan Pablo Santos Rodríguez wrote: > >> Hi! >> >> I agree with moving scope to submodules. As for keeping dependencyMgmt >> only >> for duplicated entries, I'd rather keep them all; I find easier to locate >> dependencies config if it's centralized, if it's scattered I find more >> difficult to know what libs are we using at a glance. >> >> Also, I'd like to start with submodules next week, so dependencies will >> start to be moved between submodules. >> >> br, >> juan pablo >> >> apologies on brevity, typos introduced by phone's spellchecker >> >> >
