Re: [VOTE] Release Log4j 2.7-rc2

2016-10-04 Thread Matt Sicker
+1 Compiles fine, works with my apps, signatures are good. On 3 October 2016 at 21:45, Gary Gregory wrote: > FWIW, Maven 3.0.5 and Java 7 give me "[ERROR] PermGen space -> [Help 1]" > > But with MAVEN_OPTS=-Xmx2000m -XX:MaxPermSize=384m and Maven 3.0.5 and > Java 7 it works! > > With Maven 3.3.

Re: Release Candidate artifact versioning

2016-10-04 Thread Matt Sicker
Gradle caches are in ~/.gradle/caches/modules-2/files-2.1/org.apache.logging.log4j Could be a different location in older versions of Gradle, but I'm using Gradle 2.14.1 and 3.1. On 4 October 2016 at 02:43, Mikael Ståldal wrote: > But that might not work if the project you test with uses anothe

Re: [VOTE] Release Log4j 2.7-rc1

2016-10-04 Thread Mikael Ståldal
I was able to build the site on Linux with: MAVEN_OPTS="-Xmx2000m -XX:MaxPermSize=384m" mvn site Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Java version: 1.7.0_80, vendor: Oracle Corporation Default locale: en_US, platform encoding: UTF-8 OS name: "lin

Re: Release Candidate artifact versioning

2016-10-04 Thread Steffen Offermann
BTW, would it be a problem to publish the release candidates themselves to the central repository, like some other projects do? On 10/03/2016 06:20 PM, Mikael Ståldal wrote: Why do we need to vote on the exact artifact version to release? Isn't it enough that we vote on the RC and then trust

Re: logging-log4j2 git commit: LOG4J2-1623 Configurable JVM shutdown hook timeout

2016-10-04 Thread Mikael Ståldal
That might make sense, but I propose we do that separately since it's not related to what I am working on. On Mon, Oct 3, 2016 at 11:28 PM, Gary Gregory wrote: > WRT: > > http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/7 > 05e2725/log4j-core/src/main/java/org/apache/logging/log4j/co >

[jira] [Commented] (LOG4J2-1629) Support for primitive values in StringMap

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544922#comment-15544922 ] Remko Popma commented on LOG4J2-1629: - I was looking at the Java 8 naming conventions

[jira] [Updated] (LOG4J2-1629) Support for primitive values in StringMap

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1629: Description: For some applications like financial trading systems, highly interactive games or num

Re: Shutdown timeout

2016-10-04 Thread Mikael Ståldal
Do we need a "don't wait" case? On Mon, Oct 3, 2016 at 11:35 PM, Gary Gregory wrote: > Right now, in the Configurator.shutdown 0 means do not wait at all. > > We could have: > > > 0 wait > = 0 don't wait > -1 wait forever which could map to Long.MAX_VALUE, TimeUnit.DAYS. What > where they thinki

[jira] [Commented] (LOG4J2-1629) Support for primitive values in StringMap

2016-10-04 Thread JIRA
[ https://issues.apache.org/jira/browse/LOG4J2-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544708#comment-15544708 ] Mikael Ståldal commented on LOG4J2-1629: Why not {{LongBiConsumer}} / {{LongTriCo

[jira] [Updated] (LOG4J2-1629) Support for primitive values in StringMap

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1629: Description: For some applications like financial trading systems, highly interactive games or num

[jira] [Closed] (LOG4J2-321) Provide configuration alternative to system properties

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-321. -- Resolution: Won't Fix Closing this issue. This is technically challenging with the current design: Log

[jira] [Closed] (LOG4J2-1596) Additional params on public methods break binary compatibility

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1596. --- Resolution: Won't Fix For the next release I would like to set up something like REVAPI (LOG4J2-1576)

Re: Release Candidate artifact versioning

2016-10-04 Thread Mikael Ståldal
But that might not work if the project you test with uses another build tool (Ivy, Gradle, SBT) since they might cache artifacts elsewhere. It is of cause possible to clean-up that as well, but quite some hassle. On Mon, Oct 3, 2016 at 11:32 PM, Gary Gregory wrote: > When I build and deploy RCs

[jira] [Closed] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1588. --- Resolution: Won't Fix Closing as Won't Fix since (a) a better alternative exists and (b) this behavi

[jira] [Commented] (LOG4J2-1588) Console or File Logger caches thread name, but not in older log4j2 versions

2016-10-04 Thread Remko Popma (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544625#comment-15544625 ] Remko Popma commented on LOG4J2-1588: - I agree it is not intuitive that the property