You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2013/04/11 16:29:15 UTC

[jira] [Created] (LOG4J2-206) Use the Maven group ID org.apache.logging.log4j for all artifacts.

Gary Gregory created LOG4J2-206:
-----------------------------------

             Summary: Use the Maven group ID org.apache.logging.log4j for all artifacts.
                 Key: LOG4J2-206
                 URL: https://issues.apache.org/jira/browse/LOG4J2-206
             Project: Log4j 2
          Issue Type: Bug
    Affects Versions: 2.0-beta4
         Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 08:51:28-0500)
Maven home: C:\Java\apache-maven-3.0.5\bin\..
Java version: 1.6.0_43, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_43\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
            Reporter: Gary Gregory
            Assignee: Gary Gregory
             Fix For: 2.0-beta5


Use the same Maven group ID for all artifacts: org.apache.logging.log4j. The group ID org.apache.logging.log4j.adapters is no longer used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org