Re: (Fixed) Building with Java 9

Thanks for the info and I’m glad the problem is resolved. Out of curiosity, did openjdk-9-java-amd64 on Ubuntu have the JDK and other tools like jstack, jmap, etc, or was it just the JRE? Ralph > On Jul 11, 2017, at 9:32 PM, kenneth mcfarland > wrote: > > I

(Fixed) Building with Java 9

I would just like to ask if this information would be useful for the public: On Ubuntu 16.04.2, the openjdk-9-java-amd64 via the repository does not have javac. Using openjdk-9-java-amd64 (as exposed via the toolchain-sample-linux.xml file) will result in failure, at least with sudo apt-get

Re: Log4J2-API-Java9 Build Failure

Maven reports finding the java jdk for 9 but fails. I presume it not is not an openjdk issue because I basically copied the toolchain-sample-linux.xml file to my .m2 folder. I am using maven 3.5. Thank you guys so much! [INFO]

[jira] [Commented] (LOG4J2-1973) FailoverAppenders fail to start

[ https://issues.apache.org/jira/browse/LOG4J2-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082491#comment-16082491 ] Vina Martin commented on LOG4J2-1973: - I tried to recreate this in a different way. I created a disk

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082270#comment-16082270 ] ASF GitHub Bot commented on LOG4J2-1864: Github user jvz commented on the issue:

[GitHub] logging-log4j2 issue #62: (LOG4J2-1864) Support capped collection for MongoD...

Github user jvz commented on the issue: https://github.com/apache/logging-log4j2/pull/62 https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/manual/appenders.xml is the appenders manual page which should be what you're looking for. Just follow the patterns for how to

Re: Log4J2-API-Java9 Build Failure

Somehow your tool chain is not being found. The --release option is only available in java 9. When the build runs the compile plugin should tell you that it is using the Java 9 tool chain. Ralph > On Jul 10, 2017, at 9:51 PM, kenneth mcfarland > wrote: > > I am

[jira] [Commented] (LOG4J2-1852) Plugins lookup by package is not compatible with Spring Boot jar packaging

[ https://issues.apache.org/jira/browse/LOG4J2-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082052#comment-16082052 ] Tanner Altares commented on LOG4J2-1852: Is there any update or on this issue? As stated by the

[GitHub] logging-log4j2 pull request #92: consider the StringBuilder's capacity inste...

GitHub user xnslong opened a pull request: https://github.com/apache/logging-log4j2/pull/92 consider the StringBuilder's capacity instead of content length when do the trim The trim operation aims at releasing the too much memory occupied by the `StringBuilder`. So when the

[jira] [Commented] (LOG4J2-1972) The "packages" attribute in appender configuration reporting ERROR

[ https://issues.apache.org/jira/browse/LOG4J2-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081941#comment-16081941 ] Seweryn Habdank-Wojewodzki commented on LOG4J2-1972: [~ralph.go...@dslextreme.com]

[jira] [Commented] (LOG4J2-1864) Support capped collection for MongoDB Log-Provider

[ https://issues.apache.org/jira/browse/LOG4J2-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081857#comment-16081857 ] ASF GitHub Bot commented on LOG4J2-1864: Github user codescale commented on the issue:

[GitHub] logging-log4j2 issue #62: (LOG4J2-1864) Support capped collection for MongoD...

Github user codescale commented on the issue: https://github.com/apache/logging-log4j2/pull/62 I must admit I don't know where/how I can help you to keep the docs up to date. If I'm able to help, please point me to the right location :) thanks. --- If your project is set up for it,

[GitHub] logging-log4j2 issue #82: Add a new LuceneAppender which writes logging even...

Github user liyuj commented on the issue: https://github.com/apache/logging-log4j2/pull/82 This PR does not have a corresponding issue. The code is used within our company and we think he has reusability, so it contributes to the community. The functionality has been tested