[slf4j-dev] [Bug 162] New: Group SLF4J maven artifacts by means of group ID

bugzilla-daemon at pixie.qos.ch bugzilla-daemon at pixie.qos.ch
Fri Dec 4 10:45:23 CET 2009


http://bugzilla.slf4j.org/show_bug.cgi?id=162

           Summary: Group SLF4J maven artifacts by means of group ID
           Product: SLF4J
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P1
         Component: Core API
        AssignedTo: slf4j-dev at qos.ch
        ReportedBy: chad.lajoie at switch.ch


Currently, all SLF4J maven artifacts use a single group ID.  In order to
prevent a user of a maven project from having to go out, download, and grab the
appropriate bridge (e.g. slfj4j-log4j13) and adapter (e.g. jcl-over-slf4j)
libraries the project developer may wish to include these within the project
distribution.  Mostly like this would be done by putting the bridge and adapter
artifacts in a separate directory, such as with this assembly descriptor
fragment:

<dependencySet>
    <outputDirectory>/lib/slf4j-adpater</outputDirectory>
    <includes>
        <include>org.slf4j.adapter:*</include>
     </includes>
</dependencySet>

Without having the bridge and adapter artifacts registered under separate group
IDs, however, this becomes difficult.  The project assembly author must
specifically include the core artifact and exclude the bridge and adapter
artifacts in the main lib directory, include the bridge and exclude the core
and adapter artifacts in the bridge library directory, and include the adapter
and exclude the core and bridge artifacts from the adapter library directory. 
Additionally, if any new artifacts are added the assemblies must all be updated
as well.

Therefore, it would be much simpler and cleaner if the bridge and adapter
artifacts were each registered under separate group IDs.  Note that starting
this with some given release does not break any existing maven project.  It
just means that when a maven project wants to pull in the new versions they
need to update the version and group ID in their POM instead of just the
version.


-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the slf4j-dev mailing list