Hello Chad, The package "completeness" requirement is evoked from time to time by users. It is quite understandable. If I understand correctly, you would like to change the grouping id so that your maven assembly file does not have to deal with the various slf4j-related individually but by groups? It's a good idea actually, but such grouping changes would have an impact on all downstream projects (using maven) and by transitivity on their users. It's would be quite big move. Please enter a bug report asking for this change which *may* be applied in a future release of slf4j with other breaking changes, when and *if* such breaking changes occur. Chad La Joie wrote:
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?