> On Jun 18, 2021, at 8:05 AM, Jochen Wiedmann <jochen.wiedm...@gmail.com>
> wrote:
>
> On Wed, Jun 16, 2021 at 1:31 PM Volkan Yazıcı <volkan.yaz...@gmail.com> wrote:
>
>> In essence, the build is taking more than it should. Maven "verify" is
>> taking more than half an hour and "site" is taking ages. This in addition
>> to impeding the development cycle, cripples the release process too.
>
> And why do you blame that on the build tool, rather than the
> configuration, which seems to do rather strange things. Maven's
> performance is quite decent, if given a chance. Okay, "site" may be an
> exception, but you should be able to replace Doxia with another site
> generation too,, if you are ready to drop all those nice reports, that
> Maven generates, and that users like me find very useful.
1. I am not ready to drop Maven.
2. The configuration does “strange things” because Maven doesn’t support
creating a
JPMS module, JPMS test module, and running unit tests in a single Maven module
out of the box while also avoiding
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8265826.
The “strange configuration” makes that work. Log4j-Plugins is even more
“strange”
because in addition to the above it also has to compile the annotation
processor
without the module-info.java prior to doing the “build compile” so that the
annotation
processor exists.
3. I am of the opinion that we should move most of the log4j site from
https://github.com/apache/logging-log4j2 to
https://github.com/apache/logging-log4j-site/tree/asf-staging.
Ralph
