I am not very active on the Log4j2 project any more, but I remember
how it always rubbed me that the build takes so long.
I use Gradle wherever I can in my projects. It makes the build much faster.
The problem I see with migrating the Log4j2 build to Gradle (even if
all committers would buy in to t
Oh, and though I haven't used it in over a year, SBT is the build tool
I'm most familiar with internals of (followed by Ant), so I don't have
a real preference between Maven and Gradle (both have incomprehensible
internals to me at this time).
On Fri, 31 Jan 2020 at 10:31, Matt Sicker wrote:
>
>
I've used both Maven and Gradle, switching back and forth depending on
jobs and projects. I typically lean toward Maven due to better tooling
support, but I know this is a constantly evolving area. I'd only
really be in support of a switch to Gradle if it brought more benefits
(particularly around
This is an interesting idea. I'm personally much more familiar with gradle than
I am with maven, and have worked on similar gradle plugins to avoid
incompatible logging dependencies (I have a few horror stories in this
department). Having a standard in place to prevent classpath issues would
ab
I wouldn’t say the chance is zero but it is close. I’m not sure if any of the
committers on the logging projects are as comfortable with Gradle as we are
with Maven. Although I haven’t contributed to Maven in a few years I am still
on the PMC and am quite familiar with how its internals work.
R
Hi Ralph,
Currently Gradle does not have any tooling to help a Maven build produce
Gradle Module Metadata. So a PR might be a challenge, mostly because it
will have to do a lot to limit duplication. Any chance that Log4J 2 would
consider adopting Gradle as the build tool? A migration + adoption of
We would certainly accept PRs to support the feature, assuming they include
tests that we can run to verify them. I have no idea how easy that would be to
do since Log4j 2 uses Maven as its build system.
Out of curiosity, have you mentioned the metadata to the Maven team? I know one
of the prob
Hello,
The Gradle dependency management team developed a plugin [1] in parallel to
writing a blog post on the Gradle blog [2] that shows how Gradle can help
detect invalid logging setup at build time using Gradle’s new capabilities
concept [3].
Feature wise, the plugin can detect invalid setups in
