You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Wolff Bock von Wuelfingen (Jira)" <ji...@apache.org> on 2022/08/15 16:42:00 UTC
[jira] [Commented] (LOG4J2-3573) Bring building documentation in line
[ https://issues.apache.org/jira/browse/LOG4J2-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579806#comment-17579806 ]
Wolff Bock von Wuelfingen commented on LOG4J2-3573:
---------------------------------------------------
Sidenote: A fresh clone and a call to
{code:java}
$env:JAVA_HOME_8_X64 = 'C:\Program Files\Eclipse Adoptium\jdk-8.0.345.1-hotspot'; $env:JAVA_HOME_11_X64 = 'C:\Program Files\Eclipse Adoptium\jdk-11.0.16.8-hotspot'; ./mvnw verify --global-toolchains .\workflows\maven-toolchains.xml {code}
Fails under Windows 10 x64:
{code:java}
[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] TlsSyslogAppenderTest.sendLargeLegacyBsdMessageOverTls:55->SyslogAppenderTestBase.sendAndCheckLegacyBsdMessage:71->SyslogAppenderTestBase.sendDebugLegacyBsdMessage:78 » AppenderLogging Error writing to TLS:localhost:8199 for connection localhost/127.0.0.1:8199
[ERROR] TlsSyslogAppenderTest.sendLegacyBsdMessagesOverTls:63->SyslogAppenderTestBase.sendAndCheckLegacyBsdMessages:64->SyslogAppenderTestBase.sendDebugLegacyBsdMessage:78 » AppenderLogging Error writing to TLS:localhost:8199 for connection localhost/127.0.0.1:8199
[ERROR] TlsSyslogAppenderTest.sendStructuredMessageOverTls:70->SyslogAppenderTestBase.sendAndCheckStructuredMessage:90->SyslogAppenderTestBase.sendInfoStructuredMessage:106 » AppenderLogging Error writing to TLS:localhost:8199 for connection localhost/127.0.0.1:8199
[ERROR] TlsSyslogAppenderTest.sendStructuredMessagesOverTls:77->SyslogAppenderTestBase.sendAndCheckStructuredMessages:83->SyslogAppenderTestBase.sendInfoStructuredMessage:106 » AppenderLogging Error writing to TLS:localhost:8199 for connection localhost/127.0.0.1:8199
[INFO]
[ERROR] Tests run: 2389, Failures: 0, Errors: 4, Skipped: 13
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Log4j 2 2.18.1-SNAPSHOT:
[INFO]
[INFO] Apache Log4j 2 ..................................... SUCCESS [ 2.347 s]
[INFO] Apache Log4j API Java 9 support .................... SUCCESS [ 3.417 s]
[INFO] Apache Log4j API ................................... SUCCESS [ 10.881 s]
[INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [ 1.852 s]
[INFO] Apache Log4j Core .................................. FAILURE [10:55 min]
[INFO] Apache Log4j 1.x Compatibility API ................. SKIPPED
[INFO] Apache Log4j Layout for JSON template .............. SKIPPED
[INFO] Apache Log4j Core Integration Tests ................ SKIPPED
[INFO] Apache Log4j to SLF4J Adapter ...................... SUCCESS [ 3.917 s]
[INFO] Apache Log4j SLF4J Binding ......................... SKIPPED
[INFO] Apache Log4j SLF4J 1.8+ Binding .................... SKIPPED
[INFO] Apache Log4j to JUL Bridge ......................... SUCCESS [ 3.293 s]
[INFO] Apache Log4j Commons Logging Bridge ................ SKIPPED
[INFO] Apache Log4j Flume Bridge .......................... SKIPPED
[INFO] Apache Log4j Web ................................... SKIPPED
[INFO] Apache Log4j Tag Library ........................... SKIPPED
[INFO] Apache Log4j JMX GUI ............................... SKIPPED
[INFO] Apache Log4j Samples ............................... SUCCESS [ 0.102 s]
[INFO] Apache Log4j Samples: Flume - Common ............... SKIPPED
[INFO] Apache Log4j Samples: Flume - Remote ............... SKIPPED
[INFO] Apache Log4j Samples: Flume - Embedded ............. SKIPPED
[INFO] Apache Log4j Samples: Configuration ................ SKIPPED
[INFO] Apache Log4j Samples: LoggerProperties ............. SKIPPED
[INFO] Apache Log4j BOM ................................... SUCCESS [ 0.816 s]
[INFO] Apache Log4j JDBC DBCP 2 ........................... SKIPPED
[INFO] Apache Log4j JPA ................................... SKIPPED
[INFO] Apache Log4j CouchDB ............................... SKIPPED
[INFO] Apache Log4j MongoDB 3 ............................. SKIPPED
[INFO] Apache Log4j MongoDB 4 ............................. SKIPPED
[INFO] Apache Log4j Cassandra ............................. SKIPPED
[INFO] Apache Log4j Jakarta Web ........................... SKIPPED
[INFO] Apache Log4J Performance Tests ..................... SKIPPED
[INFO] Apache Log4j Streaming Interface ................... SKIPPED
[INFO] Apache Log4j JUL Adapter ........................... SKIPPED
[INFO] Apache Log4j JDK Platform Logging Adapter .......... SKIPPED
[INFO] Apache Log4j Liquibase Binding ..................... SKIPPED
[INFO] Apache Log4j App Server Support .................... SUCCESS [ 0.945 s]
[INFO] Apache Log4j OSGi .................................. SKIPPED
[INFO] Apache Log4j Docker Library ........................ SKIPPED
[INFO] Apache Log4j Kubernetes Library .................... SKIPPED
[INFO] Apache Log4j Spring Boot Support ................... SKIPPED
[INFO] Apache Log4j Spring Cloud Config Support ........... SUCCESS [ 0.098 s]
[INFO] Apache Log4j Spring Cloud Config Client Support .... SKIPPED
[INFO] Apache Log4j Sample Configuration Service .......... SKIPPED
[INFO] Apache Log4j Spring Cloud Config Samples ........... SUCCESS [ 0.225 s]
[INFO] Apache Log4j Spring Cloud Config Sample Application SKIPPED
[INFO] Apache Log4j Jakarta SMTP .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:09 min (Wall Clock)
[INFO] Finished at: 2022-08-14T23:25:08+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M6:test (default-test) on project log4j-core:
[ERROR]
[ERROR] Please refer to C:\Users\Wolff\Idea Projects\logging-log4j2\log4j-core\target\surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :log4j-core {code}
Not sure if problem with my system, OS, or something missing in the build instructions.
> Bring building documentation in line
> ------------------------------------
>
> Key: LOG4J2-3573
> URL: https://issues.apache.org/jira/browse/LOG4J2-3573
> Project: Log4j 2
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 2.18.0
> Reporter: Wolff Bock von Wuelfingen
> Priority: Minor
>
> While looking at how to build log4j, i noticed several discrepancies; I looked at the branch release-2.x on github and on [https://logging.apache.org/log4j/2.x/build.html]
> The website seems outdated, atleast the files it lists don't exist (anymore?). Luckily the instructions in BUILDING.md work. If it is possible to somehow just display the content of the BUILDING.md in that section of the website (or just link to it) it should simplify keeping the instructions up to date.
> I think it would be good if README.md under "Building From Source" simply referred to BUILDING.md, similar to the "Contributing" section. With both changes there is then only one document to update when building procedures change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)