Github user PascalSchumacher commented on the issue:
https://github.com/apache/logging-log4j-tools/pull/1
Adding the configuration to the parent pom cause the build to fail:
```
[INFO] --- maven-jar-plugin:3.0.0:test-jar (default) @ log4j-tools ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 Tools ............................... FAILURE [
0.897 s]
[INFO] Apache Log4j Server components ..................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.926 s
[INFO] Finished at: 2017-07-31T20:24:48+02:00
[INFO] Final Memory: 16M/219M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:3.0.0:test-jar (default) on project
log4j-tools: Error assembling JAR: Manifest file:
$home\logging-log4j-tools\target\classes\META-INF\MANIFEST.MF does not exist.
-> [Help 1]
```
so I moved it to the server module.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
