I use slf4j in a number of projects, some of which are libraries. For
the libraries I like to include all the bridge (e.g. slfj4j-log4j13) and
adapter (e.g. jcl-over-slf4j) jars with the library distribution so that
people downloading the library don't have to then go and grab the slf4j
distribution as well.
However, from a maven perspective, doing this kind of a pain because
there is no way to distinguish between the core slf4j artifacts, the
bridge artifacts, and the adapter artifacts. So I would like to
recommend change the group ID for the bridge and adapter artifacts to
signify which they are. For example, using the group IDs
org.slf4j.adapter and org.slf4j.bridge.
With this I could create assemblies as followed:
<dependencySet>
<outputDirectory>/lib/slf4j-adpater</outputDirectory>
<includes>
<include>org.slf4j.adapter:*</include>
</includes>
</dependencySet>
Does this seem reasonable?
--
SWITCH
Serving Swiss Universities
--------------------------
Chad La Joie, Software Engineer, Net Services
Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland
phone +41 44 268 15 75, fax +41 44 268 15 68
[email protected], http://www.switch.ch
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
