The question I asked was, "will you be putting the slf4j, Log4j, commons-logging, and Logback into your shared library" - presumably under /usr/shared. This has nothing to do with Maven, per se. Maybe I'm not clear on what you are doing but I see two possibilities: 1. You are placing all the resultant jars in a common directory, such as /usr/share/lib, where applications will use them. This won't work for the reasons below. 2. You are building all these projects as independent entities under /usr/share. If this is the case then it sounds like you are (sort of) duplicating the Maven repository and I have no idea why this is of benefit to anyone, especially since you will only support a single version of an artifact.
I could understand this if you are building applications end users can use that are written in Java, but in that case I'd wonder why you don't just use out-of-the-box Maven and either a) just download the dependencies from the central repo or b) build the dependencies from their source and deploy them to your local repository. Of course, with the second option you would have to build several versions of the dependencies. Ralph On Jul 4, 2011, at 6:11 AM, Kasun Gajasinghe wrote: > On Mon, Jul 4, 2011 at 11:31 AM, Ralph Goers > <ralph.go...@dslextreme.com>wrote: > >> The point I am making is that if you have all those jars together something >> is not going to work correctly. SLF4J only allows one logging >> implementation. If you have all of SLF4J's jars, including the binding for >> Log4j as well as Logback, then SLF4J will throw a runtime exception. >> >> Commons Logging also has quirks. If Log4j is present then it will be used >> by default, otherwise it will do something else. >> > >> When you start dumping a whole bunch of jars together in one directory you >> had better understand how they are all going to relate to each other. >> > > I don't get it. log4j and logback won't be included in gentoo's uber-jar > since they aren't dependencies of apache-maven [1]. commons-logging and > slf4j will be integrated since they are integrated in the upstream official > build as well. What makes you think that I'm bundling together all the > available logging implementations? Is there a need to? > > [1] http://maven.apache.org/ref/2.2.1/apache-maven/dependencies.html > > Regards, > --Kasun --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
