Re: Leveraging Gradle to detect invalid logging setups

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

Re: Tentative release date for 2.13.1?

Well, that is a question for me since historically I have done almost all the releases. Matt has done some in the past but no one else has ever volunteered. Performing a release requires about 6-8 hours of my time. I have to run the build several times to validate things and verify the web site

Re: Tentative release date for 2.13.1?

On Fri, Jan 31, 2020 at 11:49 AM Rodrigo Merino wrote: > Hi all, > > Is there any general idea of when 2.13.1 will be released? I am interested > on the fix for https://issues.apache.org/jira/browse/LOG4J2-2415 And I the fix for https://issues.apache.org/jira/browse/LOG4J2-2762 :-) Gary > >

Tentative release date for 2.13.1?

Hi all, Is there any general idea of when 2.13.1 will be released? I am interested on the fix for https://issues.apache.org/jira/browse/LOG4J2-2415 Thanks in advance! Rodro -- Rodrigo Merino, Runtime Developer Av. Juana Manso 999 Piso 6, Buenos Aires,

Re: Leveraging Gradle to detect invalid logging setups

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: > >

Re: Leveraging Gradle to detect invalid logging setups

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

Re: Leveraging Gradle to detect invalid logging setups

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

Re: Leveraging Gradle to detect invalid logging setups

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

Re: Leveraging Gradle to detect invalid logging setups

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