Remove long unused dep and properties; correct doc

Author: manovotn

docs/reference/src/main/asciidoc/logging.asciidoc

@@ -4,16 +4,16 @@ endif::[]
 
 [[logging]]
 == Logging
-Weld is using link:https://developer.jboss.org/wiki/JBossLoggingTooling[JBoss Logging], an abstraction layer which provides support for the internationalization and localization of log messages and exception messages. However, JBoss Logging itself does not write any log messages. Instead, it only constructs a log message and delegates to one of the supported logging frameworks.
+Weld is using link:https://github.com/jboss-logging/jboss-logging[JBoss Logging], an abstraction layer which provides support for the internationalization and localization of log messages and exception messages. However, JBoss Logging itself does not write any log messages. Instead, it only constructs a log message and delegates to one of the supported logging frameworks.
 
 The supported "back-end" frameworks include:
 
-. link:https://developer.jboss.org/wiki/StandaloneJBossLogManager[jboss-logmanager]
-. link:http://logging.apache.org/log4j/2.x/[Log4j]
-. link:http://www.slf4j.org/[SLF4J]
+. link:https://github.com/jboss-logging/jboss-logging[jboss-logmanager]
+. link:https://logging.apache.org/log4j/2.x/[Log4j]
+. link:https://www.slf4j.org/[SLF4J]
 . JDK logging
 
-A system property `org.jboss.logging.provider` may be used to specify the logging framework directly. Supported values are `jboss`, `jdk`, `log4j` and `slf4j`. If this system property is not set, JBoss Logging will attempt to find the logging frameworks from the above-mentioned list on the classpath - the first one found is taken.
+A system property `org.jboss.logging.provider` may be used to specify the logging framework directly. Supported values are `jboss`, `jdk`, `log4j2` and `slf4j`. If this system property is not set, JBoss Logging will attempt to find the logging frameworks from the above-mentioned list on the classpath - the first one found is taken.
 
 === Java EE containers
 If using Weld with a Java EE container (e.g. WildFly) the logging configuration is under the direction of the container. You should follow the container-specific guides to change the configuration (e.g. link:http://docs.wildfly.org/14/Admin_Guide.html#Logging[WildFly Admin Guide - Logging Configuration]).

examples/se/groovy-numberguess/src/main/resources/log4j.properties

@@ -389,30 +389,12 @@
                     <groupId>org.wildfly.arquillian</groupId>
                     <artifactId>wildfly-arquillian-container-managed</artifactId>
                     <scope>test</scope>
-                    <exclusions>
-                        <exclusion>
-                            <groupId>org.jboss.arquillian.core</groupId>
-                            <artifactId>arquillian-core-spi</artifactId>
-                        </exclusion>
-                        <exclusion>
-                            <groupId>org.jboss.arquillian.core</groupId>
-                            <artifactId>arquillian-core-api</artifactId>
-                        </exclusion>
-                        <exclusion>
-                            <groupId>org.jboss.logmanager</groupId>
-                            <artifactId>log4j-jboss-logmanager</artifactId>
-                        </exclusion>
-                    </exclusions>
                 </dependency>
                 <dependency>
                     <groupId>org.jboss.arquillian.protocol</groupId>
                     <artifactId>arquillian-protocol-servlet-jakarta</artifactId>
                     <scope>test</scope>
                 </dependency>
-                <dependency>
-                    <groupId>log4j</groupId>
-                    <artifactId>log4j</artifactId>
-                </dependency>
             </dependencies>
             <build>
                 <resources>

examples/se/numberguess/src/main/resources/log4j.properties

@@ -85,7 +85,6 @@
         <jsp.api.version>4.0.0</jsp.api.version>
         <jstl.api.version>3.0.2</jstl.api.version>
         <junit.version>4.13.2</junit.version>
-        <log4j.version>1.2.17</log4j.version>
         <shrinkwrap.version>1.2.6</shrinkwrap.version>
         <shrinkwrap.resolver.version>3.3.4</shrinkwrap.resolver.version>
         <spotbugs-maven-plugin.version>4.9.8.2</spotbugs-maven-plugin.version>
@@ -274,10 +273,6 @@
                 <artifactId>wildfly-arquillian-common</artifactId>
                 <version>${wildfly.arquillian.version}</version>
                 <exclusions>
-                    <exclusion>
-                        <groupId>org.jboss.logmanager</groupId>
-                        <artifactId>log4j-jboss-logmanager</artifactId>
-                    </exclusion>
                     <exclusion>
                         <groupId>org.slf4j</groupId>
                         <artifactId>slf4j-api</artifactId>
@@ -417,12 +412,6 @@
                 <version>${jsp.api.version}</version>
             </dependency>
 
-            <dependency>
-                <groupId>log4j</groupId>
-                <artifactId>log4j</artifactId>
-                <version>${log4j.version}</version>
-            </dependency>
-
             <dependency>
                 <groupId>io.smallrye</groupId>
                 <artifactId>jandex</artifactId>