LOG4J2-2575: CronExpression.getTimeBefore() bug

2019-05-27 Thread Nathan Friess
Hi, I submitted https://issues.apache.org/jira/browse/LOG4J2-2575 along with a patch a while ago and there hasn't been any activity on it since then. The basic problem is that sometimes timestamp variables have milliseconds set in them, such as the argument to getTimeBefore() when used to ro

Re: [logging-log4j-audit] branch LOG4J2-2579 updated (8fcfbb5 -> 998525c)

2019-05-27 Thread Matt Sicker
It's typically not a great idea to use force push in the main repositories as they can be shared between people. Whenever I like to use force push, I usually only do it on my own forks before making a PR. I don't think anyone else is using this branch, but it's typically a good idea to avoid force

Re: [Log4j] Groovy Configuration DSL

2019-05-27 Thread Matt Sicker
Update: latest patches for IntelliJ have made my computer functional again! Going to look at this again today. On Tue, May 7, 2019 at 10:11, Matt Sicker wrote: > A Kotlin DSL would be pretty awesome. We’d first need a good way to > generate all the relevant type metadata to do code generation. O

Re: NullPointerException in DefaultMergeStrategy

2019-05-27 Thread Gaurav
On 2019/05/27 12:21:38, Gary Gregory wrote: > Ralph, why not add null-checks in the loops of the merge methods? > > Gary > > On Mon, May 27, 2019 at 4:28 AM Gaurav wrote: > > > > > > > On 2019/05/24 19:16:33, Ralph Goers wrote: > > > Composite configuration implies that you are merging mu

Re: NullPointerException in DefaultMergeStrategy

2019-05-27 Thread Gary Gregory
Ralph, why not add null-checks in the loops of the merge methods? Gary On Mon, May 27, 2019 at 4:28 AM Gaurav wrote: > > > On 2019/05/24 19:16:33, Ralph Goers wrote: > > Composite configuration implies that you are merging multiple > configuration files. Yes, it would appear that the configura

Re: NullPointerException in DefaultMergeStrategy

2019-05-27 Thread Gaurav
On 2019/05/24 19:16:33, Ralph Goers wrote: > Composite configuration implies that you are merging multiple configuration > files. Yes, it would appear that the configuration being merged has one node > with no configuration under it. > > If you only have a single configuration this shouldn