Hey all, Apachecon has been ended so I am following the promise I did - I’ve taken a look on the log4j build to check what’s going on with OSGi stuff. Currently OSGi bundles are split from main log4j-core which I think leads to maintanance trouble also number of dependencies of log4j-core seems to be very high. If we could split the log4j-core into smaller modules (mongodb, jms, jmx, web) then there will be no need to keep log4j-osgi and it’s submodules. According to maven guides [1] "Optional dependencies are used when it's not really possible (for whatever reason) to split a project up into sub-modules”, I think it will also make library design much more clear and will avoid making unecessary inner code deps. Seems that big, aggregate modules, are always grow to size which require major work to split them to make both: maintanance and community involvement possible.
[1] https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html Cheers, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org
