Re: Import Ordering - ImpSort

[kenneth mcfarland]

Hi Matt, I opened a pull request that contains the maven plugin we looked
at.

See LOG4J2-2086. I tested this locally under the API folder and it rocks.

I know an IDE can do this, but not an entire repository and force it on
every build. Nobody can manually verify every file or guarantee other
developers will be consistent so this automation is fantastic.

On Oct 14, 2017 11:44 AM, "kenneth mcfarland" <kennethpmcfarl...@gmail.com>
wrote:

> Thank you Matt, I will try provide a patch by the end of the weekend.
>
> Cheers,
> Kenneth
>
>
> On Oct 14, 2017 11:02 AM, "Matt Sicker" <boa...@gmail.com> wrote:
>
>> That looks like it could be useful for sure. It could help avoid merge
>> conflicts. I say go for it and provide a patch!
>>
>> On 13 October 2017 at 21:57, kenneth mcfarland <
>> kennethpmcfarl...@gmail.com>
>> wrote:
>>
>> > My bad, here is a link sir.
>> >
>> > http://code.revelc.net/impsort-maven-plugin/
>> >
>> > On Fri, Oct 13, 2017 at 7:35 PM, Matt Sicker <boa...@gmail.com> wrote:
>> >
>> > > What's the plugin? I like the idea in theory at least. I've been
>> dragged
>> > > into import-related formatting wars in past jobs, and having a
>> consistent
>> > > way to handle them would be great (although I think you can configure
>> > > checkstyle to enforce it, checkstyle doesn't actually format anything
>> for
>> > > you).
>> > >
>> > > On 13 October 2017 at 20:20, kenneth mcfarland <
>> > > kennethpmcfarl...@gmail.com>
>> > > wrote:
>> > >
>> > > > Greetings,
>> > > >
>> > > > I found what I believe could be a useful plugin to make consistency
>> > > > requirements with respect to import ordering. This would impose a
>> > strict
>> > > > ordering based on a defined file that stating the rules. This is
>> > > currently
>> > > > used with Apache Fluo, and thought it might be useful here.
>> > > >
>> > > > Before adding a JIRA I felt I would ask the community. Thank you!
>> > > >
>> > > > Sincerely,
>> > > > Kenneth McFarland
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Matt Sicker <boa...@gmail.com>
>> > >
>> >
>>
>>
>>
>> --
>> Matt Sicker <boa...@gmail.com>
>>
>

Re: Planning out what we can do to get Chainsaw back in the game

[kenneth mcfarland]

Greetings,

I have been trying to find someone who can do the Apache mentor program
with me (link provided). The mentor only does roughly 1/4 the time of the
mentee, the mentee comes prepared to dedicate the time and put the work in
and provide progress reports etc.. GSoC is over obviously, but these
projects are designed to be started whenever the team is ready.

This would provide a great opportunity to get developers that are
interested, and utilize this mentorship program. It will look good on a
reference for both parties and can be very rewarding with mentees becoming
committers etc..

I am personally very interested in this, and given the nature of the
project, it can easily be done on a laptop making the entry barrier low to
other students such as myself.

https://community.apache.org/mentoringprogramme.html

On Sat, Oct 14, 2017 at 11:48 AM, Matt Sicker  wrote:

> On 14 October 2017 at 13:22, Ralph Goers 
> wrote:
>
> > I’ve worked with JavaFX. It is pretty easy. I have zero interest in
> > working with Swing.
> >
>
> Good to know! For Kotlin support, this project looks handy: <
> https://github.com/edvin/tornadofx>. For Scala support, there's this: <
> http://www.scalafx.org/>. The extent of my current JavaFX knowledge is
> basically that I know there are some sort of psuedo-XML files to describe
> the GUI (or you can use the API directly), and that it uses CSS to some
> extent.
>
>
> > I’d prefer to get away from WebStart. I think that may have been what
> hung
> > up Scott in the first place as he needed a cert. Some of the other
> > technologies for binary deployment make sense to me.
> >
>
> Infra has an official way to sign things for this now, so it might not be
> as bad as back when Scott was trying to get support for it in the first
> place. With Java 9, I think it'll be easier to bundle up .exe/.app files
> for Windows and macOS, and GNU/Linux still has a million ways to package
> things, but there are some maven plugins out there to create some common
> ones (rpm, deb, etc.). There's also Flatpak  for that
> as well. Distributing them from dist.a.o works fine, though distributing in
> app stores generally requires a signing key the same way that webstart
> does.
>
>
> > To be honest, I’ve never run Chainsaw or Lillith. I am not sure how they
> > differ. I am not a big fan of having two projects that do exactly the
> same
> > thing so I’d like some understanding of what they do and how they differ.
> >
>
> Most of my log viewing happens either via console programs (tail, grep,
> clog, tried out some others that I can't remember) or via shitty web GUIs
> (Kibana, Graylog, Splunk, etc.). If I could find or help build a GUI that
> works better for that, then that'd be great. I'm also not a fan of the
> whole "embed Chrome and call it a native app" movement going on with
> Electron; even Java is lightweight on the desktop in comparison!
>
> --
> Matt Sicker 
>

Re: Import Ordering - ImpSort

[kenneth mcfarland]

Thank you Matt, I will try provide a patch by the end of the weekend.

Cheers,
Kenneth


On Oct 14, 2017 11:02 AM, "Matt Sicker" <boa...@gmail.com> wrote:

> That looks like it could be useful for sure. It could help avoid merge
> conflicts. I say go for it and provide a patch!
>
> On 13 October 2017 at 21:57, kenneth mcfarland <
> kennethpmcfarl...@gmail.com>
> wrote:
>
> > My bad, here is a link sir.
> >
> > http://code.revelc.net/impsort-maven-plugin/
> >
> > On Fri, Oct 13, 2017 at 7:35 PM, Matt Sicker <boa...@gmail.com> wrote:
> >
> > > What's the plugin? I like the idea in theory at least. I've been
> dragged
> > > into import-related formatting wars in past jobs, and having a
> consistent
> > > way to handle them would be great (although I think you can configure
> > > checkstyle to enforce it, checkstyle doesn't actually format anything
> for
> > > you).
> > >
> > > On 13 October 2017 at 20:20, kenneth mcfarland <
> > > kennethpmcfarl...@gmail.com>
> > > wrote:
> > >
> > > > Greetings,
> > > >
> > > > I found what I believe could be a useful plugin to make consistency
> > > > requirements with respect to import ordering. This would impose a
> > strict
> > > > ordering based on a defined file that stating the rules. This is
> > > currently
> > > > used with Apache Fluo, and thought it might be useful here.
> > > >
> > > > Before adding a JIRA I felt I would ask the community. Thank you!
> > > >
> > > > Sincerely,
> > > > Kenneth McFarland
> > > >
> > >
> > >
> > >
> > > --
> > > Matt Sicker <boa...@gmail.com>
> > >
> >
>
>
>
> --
> Matt Sicker <boa...@gmail.com>
>

Re: Import Ordering - ImpSort

[kenneth mcfarland]

My bad, here is a link sir.

http://code.revelc.net/impsort-maven-plugin/

On Fri, Oct 13, 2017 at 7:35 PM, Matt Sicker <boa...@gmail.com> wrote:

> What's the plugin? I like the idea in theory at least. I've been dragged
> into import-related formatting wars in past jobs, and having a consistent
> way to handle them would be great (although I think you can configure
> checkstyle to enforce it, checkstyle doesn't actually format anything for
> you).
>
> On 13 October 2017 at 20:20, kenneth mcfarland <
> kennethpmcfarl...@gmail.com>
> wrote:
>
> > Greetings,
> >
> > I found what I believe could be a useful plugin to make consistency
> > requirements with respect to import ordering. This would impose a strict
> > ordering based on a defined file that stating the rules. This is
> currently
> > used with Apache Fluo, and thought it might be useful here.
> >
> > Before adding a JIRA I felt I would ask the community. Thank you!
> >
> > Sincerely,
> > Kenneth McFarland
> >
>
>
>
> --
> Matt Sicker <boa...@gmail.com>
>

Re: [jira] [Commented] (LOG4J2-1479) Help Apache Spark project to upgrade from Log4j 1.x to 2.x

[kenneth mcfarland]

ZooKeeper uses Log4j1.2 it needs some love too. I read end of life was 2015?

On Oct 3, 2017 9:12 AM, "Remko Popma (JIRA)"  wrote:

>
> [ https://issues.apache.org/jira/browse/LOG4J2-1479?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel=16189914#comment-16189914 ]
>
> Remko Popma commented on LOG4J2-1479:
> -
>
> If people are looking to help out, the most proactive way to help is to go
> to the issue tracker of such projects and provide a patch or pull request
> that migrates the project to Log4j2. Ideally with unit tests to ensure the
> changes work and don't break anything.
>
> > Help Apache Spark project to upgrade from Log4j 1.x to 2.x
> > --
> >
> > Key: LOG4J2-1479
> > URL: https://issues.apache.org/jira/browse/LOG4J2-1479
> > Project: Log4j 2
> >  Issue Type: Sub-task
> >Reporter: Mikael Ståldal
> >Assignee: Mikael Ståldal
> >
>
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

Re: [ANNOUNCE] Apache Log4j 2.9.0 released

[kenneth mcfarland]

rDestination interface and use these methods in TextEncoderHelper
where possible to prepare for future enhancements to reduce lock
contention. Thanks to Roman Leventov.
> LOG4J2-1442 <https://issues.apache.org/jira/browse/LOG4J2-1442>: Generic
HTTP appender.
> LOG4J2-1935 <https://issues.apache.org/jira/browse/LOG4J2-1935>: Add
with(String, primitive) methods to org.apache.logging.log4j.
message.MapMessage.
> LOG4J2-1930 <https://issues.apache.org/jira/browse/LOG4J2-1930>: Add
forEach() methods to org.apache.logging.log4j.message.MapMessage.
> LOG4J2-1932 <https://issues.apache.org/jira/browse/LOG4J2-1932>: Add
containsKey() methods to org.apache.logging.log4j.message.MapMessage.
> LOG4J2-1854 <https://issues.apache.org/jira/browse/LOG4J2-1854>: Support
null byte delimiter in GelfLayout. Thanks to Xavier Jodoin.
> LOG4J2-1359 <https://issues.apache.org/jira/browse/LOG4J2-1359>: Add
support for Java 9 StackWalker.
> LOG4J2-1880 <https://issues.apache.org/jira/browse/LOG4J2-1880>: Warn
when a configuration file for an inactive ConfigurationFactory is found.
> LOG4J2-1855 <https://issues.apache.org/jira/browse/LOG4J2-1855>: Add an
optional random delay in TimeBasedTriggeringPolicy Thanks to Anthony Maire.
> LOG4J2-1860 <https://issues.apache.org/jira/browse/LOG4J2-1860>: Shortcut
to add Property and KeyValuePair component in ConfigurationBuilder.
> LOG4J2-1294 <https://issues.apache.org/jira/browse/LOG4J2-1294>: The JMS
Appender should use a JMS MapMessage for a Log4j MapMessage.
> <https://github.com/apache/logging-log4j2/blob/master/
RELEASE-NOTES.md#fixed-bugs>Fixed Bugs
>
> LOG4J2-1833 <https://issues.apache.org/jira/browse/LOG4J2-1833>: Prevent
NullPointerException when a file name is specified with the
DirectWriteRolloverStrategy.
> LOG4J2-2018 <https://issues.apache.org/jira/browse/LOG4J2-2018>: Fix
incorrect documentation for LoggerNameLevelRewritePolicy.
> LOG4J2-922 <https://issues.apache.org/jira/browse/LOG4J2-922>: Parameter
of mdcId in SyslogAppender has no default value. Thanks to angus.aqlu, Paul
Burrowes.
> LOG4J2-2001 <https://issues.apache.org/jira/browse/LOG4J2-2001>:
StyleConverter.newInstance argument validation is incorrect. Thanks to Paul
Burrowes.
> LOG4J2-1999 <https://issues.apache.org/jira/browse/LOG4J2-1999>:
HighlightConverter converts all unrecognized levels to DEBUG. Thanks to
Paul Burrowes.
> LOG4J2-2013 <https://issues.apache.org/jira/browse/LOG4J2-2013>:
SslSocketManager does not apply SSLContext on TCP reconnect. Thanks to
Taylor Patton, Gary Gregory.
> LOG4J2-2016 <https://issues.apache.org/jira/browse/LOG4J2-2016>: Mark
FileRenameAction as successful when using alternative ways to move files.
Thanks to Benjamin Jaton.
> LOG4J2-2012 <https://issues.apache.org/jira/browse/LOG4J2-2012>: No
compression when using a separate drive in Linux. Thanks to Benjamin Jaton.
> LOG4J2-1888 <https://issues.apache.org/jira/browse/LOG4J2-1888>: Log4j
throws a java.nio.charset.UnsupportedCharsetException: cp65001. Thanks to
Misagh Moayyed.
> LOG4J2-1990 <https://issues.apache.org/jira/browse/LOG4J2-1990>:
ConcurrentModificationException logging a parameter of type Map. Thanks to
Philippe Mouawad.
> LOG4J2-1311 <https://issues.apache.org/jira/browse/LOG4J2-1311>:
SocketAppender will lose several events after re-connection to server.
Thanks to Xibing Liang.
> LOG4J2-1977 <https://issues.apache.org/jira/browse/LOG4J2-1977>: Consider
the StringBuilder's capacity instead of content length when trimming.
Thanks to Jerry xnslong.
> LOG4J2-1971 <https://issues.apache.org/jira/browse/LOG4J2-1971>: Register
log4j-core as an OSGi service. Skip tests for LOG4J2-1766 on MacOS. Use
group "staff" for LOG4J2-1699 test on MacOS.
> LOG4J2-1994 <https://issues.apache.org/jira/browse/LOG4J2-1994>:
TcpSocketServer does not close accepted Sockets.
> LOG4J2-1987 <https://issues.apache.org/jira/browse/LOG4J2-1987>: Log4J
JUL Bridge and RMI Security Manager causes access denied
("java.util.logging.LoggingPermission" "control") Thanks to Andreas Felder.
> LOG4J2-1982 <https://issues.apache.org/jira/browse/LOG4J2-1982>:
Log4j-config.xsd only allows one AppenderRef element for each Logger
element. Thanks to Christoph Lembeck.
> LOG4J2-1985 <https://issues.apache.org/jira/browse/LOG4J2-1985>: Fix
default buffer size to match documentation (from 8102 to 8192 a.k.a. 8KB.)
Thanks to Kenneth McFarland.
> LOG4J2-1912 <https://issues.apache.org/jira/browse/LOG4J2-1912>:
CompositeConfiguration logs warning "Unable to determine URI for
configuration." However, the reconfiguration is completed. Thanks to R Ri.
> LOG4J2-1964 <https://issues.apache.org/jira/browse/LOG4J2-1964>: Dynamic
reconfiguration does not work for filePa

[jira] [Closed] (LOG4J2-1997) Test classes do not close resources and use deprecated methods

[kenneth mcfarland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kenneth mcfarland closed LOG4J2-1997.
-
Resolution: Fixed

Someone else can fix this mess.

> Test classes do not close resources and use deprecated methods
> --
>
> Key: LOG4J2-1997
> URL: https://issues.apache.org/jira/browse/LOG4J2-1997
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.9
> Environment: Ubuntu Linux 16.04.2 x64 
> Oracle Java 8 with Hotspot
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Some of the test classes are not closing resources and / or using deprecated 
> methods. I have modified a number of files to keep the test cases looking 
> clean. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [GitHub] logging-log4j2 pull request #106: LOG4J2-1997 This cleans up the entire test...

[kenneth mcfarland]

Can you be more specific as your own style guide forbids wildcards..

Thanks Matt!

On Aug 7, 2017 9:13 PM, "Matt Sicker" <boa...@gmail.com> wrote:

> Did you even look at the style guide before going through with this?
>
> http://logging.apache.org/log4j/2.x/javastyle.html
>
> We use a code formatter, too, which gets you most of the way there. If you
> want to help fix up style issues, contributing a better checkstyle
> configuration and fixing the errors would be more useful IMO.
>
> And I think you should really take a look through the code of conduct:
>
> http://apache.org/foundation/policies/conduct.html
>
> On 7 August 2017 at 22:20, kenneth mcfarland <kennethpmcfarl...@gmail.com>
> wrote:
>
> > The comment " this would look so cool using lambdas " is in my opinion
> > childish.
> >
> > I did not know the order of static imports was incorrect, I'm used to
> > seeing them at top almost every other project but a simple copy paste is
> > fine. Even the Oracle examples do it but I really don't think it's worth
> > analyzing, I'll change it.
> >
> > Other capitalization fixes were made, so logs to console had consistent
> > casing, again based off the majority of existing classes and the test
> class
> > itself.
> >
> > The other comments simply add a more robust output.
> >
> > Respectful yours,
> > Kenneth
> >
> >
> >
> > On Aug 7, 2017 5:49 PM, "rgoers" <g...@git.apache.org> wrote:
> >
> > > Github user rgoers commented on a diff in the pull request:
> > >
> > > https://github.com/apache/logging-log4j2/pull/106#
> > > discussion_r131797894
> > >
> > > --- Diff: log4j-core/src/test/java/org/apache/logging/log4j/core/
> > LogEventFactoryTest.java
> > > ---
> > > @@ -87,7 +88,7 @@ public void before() {
> > >  @Test
> > >  public void testEvent() {
> > >  final org.apache.logging.log4j.Logger logger =
> > > context.getLogger("org.apache.test.LogEventFactory");
> > > -logger.error("error message");
> > > +logger.error("Error message");
> > > --- End diff --
> > >
> > > Why does this message need to be changed?
> > >
> > >
> > > ---
> > > If your project is set up for it, you can reply to this email and have
> > your
> > > reply appear on GitHub as well. If your project does not have this
> > feature
> > > enabled and wishes so, or if the feature is enabled but not working,
> > please
> > > contact infrastructure at infrastruct...@apache.org or file a JIRA
> > ticket
> > > with INFRA.
> > > ---
> > >
> >
>
>
>
> --
> Matt Sicker <boa...@gmail.com>
>

Re: [GitHub] logging-log4j2 pull request #106: LOG4J2-1997 This cleans up the entire test...

[kenneth mcfarland]

The comment " this would look so cool using lambdas " is in my opinion
childish.

I did not know the order of static imports was incorrect, I'm used to
seeing them at top almost every other project but a simple copy paste is
fine. Even the Oracle examples do it but I really don't think it's worth
analyzing, I'll change it.

Other capitalization fixes were made, so logs to console had consistent
casing, again based off the majority of existing classes and the test class
itself.

The other comments simply add a more robust output.

Respectful yours,
Kenneth



On Aug 7, 2017 5:49 PM, "rgoers"  wrote:

> Github user rgoers commented on a diff in the pull request:
>
> https://github.com/apache/logging-log4j2/pull/106#
> discussion_r131797894
>
> --- Diff: 
> log4j-core/src/test/java/org/apache/logging/log4j/core/LogEventFactoryTest.java
> ---
> @@ -87,7 +88,7 @@ public void before() {
>  @Test
>  public void testEvent() {
>  final org.apache.logging.log4j.Logger logger =
> context.getLogger("org.apache.test.LogEventFactory");
> -logger.error("error message");
> +logger.error("Error message");
> --- End diff --
>
> Why does this message need to be changed?
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Simple Patch Log4j2-1997

[kenneth mcfarland]

https://github.com/apache/logging-log4j2/pull/106

Patch

[kenneth mcfarland]

I am politely asking for someone to merge my patch. I realize it is 31
files but the reading is at a 1st grade level and it makes our code look
professional. Thanks.

Re: [jira] [Updated] (LOG4J2-1922) SocketHandler leaks connection if EOFException is thrown

[kenneth mcfarland]

Have you ran it with 2.9?

On Aug 2, 2017 11:40 PM, "Kohei Tamura (JIRA)"  wrote:


 [ https://issues.apache.org/jira/browse/LOG4J2-1922?page=
com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kohei Tamura updated LOG4J2-1922:
-
Affects Version/s: (was: 2.7)
   2.3

> SocketHandler leaks connection if EOFException is thrown
> 
>
> Key: LOG4J2-1922
> URL: https://issues.apache.org/jira/browse/LOG4J2-1922
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.3
>Reporter: Kohei Tamura
>
> SocketHandler should close the input stream in the finally block.
> {code:title=TcpSocketServer.java|borderStyle=solid}
> /**
>  * Thread that processes the events.
>  */
> private class SocketHandler extends Thread {
> private final T inputStream;
> private volatile boolean shutdown = false;
> public SocketHandler(final Socket socket) throws IOException {
> this.inputStream = logEventInput.wrapStream(
socket.getInputStream());
> }
> @Override
> public void run() {
> boolean closed = false;
> try {
> try {
> while (!shutdown) {
> logEventInput.logEvents(inputStream,
TcpSocketServer.this);
> }
> } catch (final EOFException e) {
> closed = true;
> } catch (final OptionalDataException e) {
> logger.error("OptionalDataException eof=" + e.eof + "
length=" + e.length, e);
> } catch (final IOException e) {
> logger.error("IOException encountered while reading
from socket", e);
> }
> if (!closed) {
> try {
> inputStream.close();
> } catch (final Exception ex) {
> // Ignore the exception;
> }
> }
> } finally {
> handlers.remove(Long.valueOf(getId()));
> }
> }
> public void shutdown() {
> this.shutdown = true;
> interrupt();
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [GitHub] logging-log4j2 pull request #104: LOG4J-1997 Cleanup of deprecated methods, ...

[kenneth mcfarland]

The intent was to remove the warnings that Eclipse was showing for the
unused field.

On Aug 1, 2017 2:45 PM, "garydgregory"  wrote:

> Github user garydgregory commented on a diff in the pull request:
>
> https://github.com/apache/logging-log4j2/pull/104#
> discussion_r130737396
>
> --- Diff: 
> log4j-core/src/test/java/org/apache/logging/log4j/core/appender/HangingAppender.java
> ---
> @@ -90,4 +90,8 @@ public boolean stop(final long timeout, final
> TimeUnit timeUnit) {
>  setStopped();
>  return true;
>  }
> +
> +   public static long getSerialversionuid() {
> --- End diff --
>
> None that I can think of...
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

[jira] [Commented] (LOG4J2-1997) Test classes do not close resources and use deprecated methods

[kenneth mcfarland (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108338#comment-16108338
 ] 

kenneth mcfarland commented on LOG4J2-1997:
---

https://github.com/apache/logging-log4j2/pull/104 this pr uses try with 
resources as advised.


> Test classes do not close resources and use deprecated methods
> --
>
> Key: LOG4J2-1997
> URL: https://issues.apache.org/jira/browse/LOG4J2-1997
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.9
> Environment: Ubuntu Linux 16.04.2 x64 
> Oracle Java 8 with Hotspot
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Some of the test classes are not closing resources and / or using deprecated 
> methods. I have modified a number of files to keep the test cases looking 
> clean. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LOG4J2-1997) Test classes do not close resources and use deprecated methods

[kenneth mcfarland (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108267#comment-16108267
 ] 

kenneth mcfarland commented on LOG4J2-1997:
---

Great point, I'll clean it up after dinner Gary.




> Test classes do not close resources and use deprecated methods
> --
>
> Key: LOG4J2-1997
> URL: https://issues.apache.org/jira/browse/LOG4J2-1997
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 2.9
> Environment: Ubuntu Linux 16.04.2 x64 
> Oracle Java 8 with Hotspot
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> Some of the test classes are not closing resources and / or using deprecated 
> methods. I have modified a number of files to keep the test cases looking 
> clean. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (LOG4J2-1997) Test classes do not close resources and use deprecated methods

[kenneth mcfarland (JIRA)]

kenneth mcfarland created LOG4J2-1997:
-

 Summary: Test classes do not close resources and use deprecated 
methods
 Key: LOG4J2-1997
 URL: https://issues.apache.org/jira/browse/LOG4J2-1997
 Project: Log4j 2
  Issue Type: Bug
  Components: Core
Affects Versions: 2.9
 Environment: Ubuntu Linux 16.04.2 x64 
Oracle Java 8 with Hotspot
Reporter: kenneth mcfarland
 Fix For: 2.9


Some of the test classes are not closing resources and / or using deprecated 
methods. I have modified a number of files to keep the test cases looking 
clean. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (LOG4J2-1993) Fix compiler warnings in LoggerConfigTest

[kenneth mcfarland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kenneth mcfarland closed LOG4J2-1993.
-

> Fix compiler warnings in LoggerConfigTest
> -
>
> Key: LOG4J2-1993
> URL: https://issues.apache.org/jira/browse/LOG4J2-1993
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 2.9
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I have updated this test class to remove type warnings. Deprecated methods 
> where not intentionally used have been replaced with builder methods.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LOG4J2-1993) Update LoggerConfigTest

[kenneth mcfarland (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16105335#comment-16105335
 ] 

kenneth mcfarland commented on LOG4J2-1993:
---

Here is the PR to close this:
https://github.com/apache/logging-log4j2/pull/101

Also, please assign to me if possible so that future employers can look and 
clearly see I closed this issue.

> Update LoggerConfigTest
> ---
>
> Key: LOG4J2-1993
> URL: https://issues.apache.org/jira/browse/LOG4J2-1993
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: Core
>Affects Versions: 2.9
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I have updated this test class to remove type warnings. Deprecated methods 
> where not intentionally used have been replaced with builder methods.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (LOG4J2-1993) Update LoggerConfigTest

[kenneth mcfarland (JIRA)]

kenneth mcfarland created LOG4J2-1993:
-

 Summary: Update LoggerConfigTest
 Key: LOG4J2-1993
 URL: https://issues.apache.org/jira/browse/LOG4J2-1993
 Project: Log4j 2
  Issue Type: Improvement
  Components: Core
Affects Versions: 2.9
Reporter: kenneth mcfarland
 Fix For: 2.9


I have updated this test class to remove type warnings. Deprecated methods 
where not intentionally used have been replaced with builder methods.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (LOG4J2-1991) Refactor SimpleMessage to use ternary statements where appropriate

[kenneth mcfarland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kenneth mcfarland closed LOG4J2-1991.
-

> Refactor SimpleMessage to use ternary statements where appropriate
> --
>
> Key: LOG4J2-1991
> URL: https://issues.apache.org/jira/browse/LOG4J2-1991
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: API
>Affects Versions: 2.9
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> I have cleaned up and refactored a couple blocks of code to be more readable 
> without changing fundamental mechanics. The changes make it easier to read 
> and reduce 7 lines of code bloat.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (LOG4J2-1991) Refactor SimpleMessage to use ternary statements where appropriate

[kenneth mcfarland (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16102716#comment-16102716
 ] 

kenneth mcfarland commented on LOG4J2-1991:
---

Link to PR : https://github.com/apache/logging-log4j2/pull/100

> Refactor SimpleMessage to use ternary statements where appropriate
> --
>
> Key: LOG4J2-1991
> URL: https://issues.apache.org/jira/browse/LOG4J2-1991
> Project: Log4j 2
>  Issue Type: Improvement
>  Components: API
>Affects Versions: 2.9
>    Reporter: kenneth mcfarland
> Fix For: 2.9
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> I have cleaned up and refactored a couple blocks of code to be more readable 
> without changing fundamental mechanics. The changes make it easier to read 
> and reduce 7 lines of code bloat.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (LOG4J2-1991) Refactor SimpleMessage to use ternary statements where appropriate

[kenneth mcfarland (JIRA)]

kenneth mcfarland created LOG4J2-1991:
-

 Summary: Refactor SimpleMessage to use ternary statements where 
appropriate
 Key: LOG4J2-1991
 URL: https://issues.apache.org/jira/browse/LOG4J2-1991
 Project: Log4j 2
  Issue Type: Improvement
  Components: API
Affects Versions: 2.9
Reporter: kenneth mcfarland
 Fix For: 2.9


I have cleaned up and refactored a couple blocks of code to be more readable 
without changing fundamental mechanics. The changes make it easier to read and 
reduce 7 lines of code bloat.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (LOG4J2-1989) Javadoc for AbstractTriggeringPolicy is hard to understand

[kenneth mcfarland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kenneth mcfarland closed LOG4J2-1989.
-

All good in the hood.

> Javadoc for AbstractTriggeringPolicy is hard to understand
> --
>
> Key: LOG4J2-1989
> URL: https://issues.apache.org/jira/browse/LOG4J2-1989
> Project: Log4j 2
>  Issue Type: Documentation
>  Components: Documentation
>Affects Versions: 2.9
>    Reporter: kenneth mcfarland
>  Labels: documentation
> Fix For: 2.9
>
>   Original Estimate: 2m
>  Remaining Estimate: 2m
>
> The javadoc comment for AbstractTriggeringPolicy is simply hard to make out. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (LOG4J2-1989) Javadoc for AbstractTriggeringPolicy is hard to understand

[kenneth mcfarland (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kenneth mcfarland updated LOG4J2-1989:
--

This is more than a typo so this is my first time filing a JIRA. Here is the PR 
I filed that will close this.

https://github.com/apache/logging-log4j2/pull/99

> Javadoc for AbstractTriggeringPolicy is hard to understand
> --
>
> Key: LOG4J2-1989
> URL: https://issues.apache.org/jira/browse/LOG4J2-1989
> Project: Log4j 2
>  Issue Type: Documentation
>  Components: Documentation
>Affects Versions: 2.9
>    Reporter: kenneth mcfarland
>  Labels: documentation
>   Original Estimate: 2m
>  Remaining Estimate: 2m
>
> The javadoc comment for AbstractTriggeringPolicy is simply hard to make out. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (LOG4J2-1989) Javadoc for AbstractTriggeringPolicy is hard to understand

[kenneth mcfarland (JIRA)]

kenneth mcfarland created LOG4J2-1989:
-

 Summary: Javadoc for AbstractTriggeringPolicy is hard to understand
 Key: LOG4J2-1989
 URL: https://issues.apache.org/jira/browse/LOG4J2-1989
 Project: Log4j 2
  Issue Type: Documentation
  Components: Documentation
Affects Versions: 2.9
Reporter: kenneth mcfarland


The javadoc comment for AbstractTriggeringPolicy is simply hard to make out. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[kenneth mcfarland]

Ok I'm blind but maybe can add a commit() after line 193 right after
addDocument() to be aggressive

On Jul 24, 2017 8:54 PM, "garydgregory" <g...@git.apache.org> wrote:

> Github user garydgregory commented on the issue:
>
> https://github.com/apache/logging-log4j2/pull/82
>
> Is what is happening
> in org.apache.logging.log4j.lucene5.appender.LuceneAppender.stop(long,
> TimeUnit) not good enough?
>
> Gary
>
> On Mon, Jul 24, 2017 at 8:30 PM, asfbot <notificati...@github.com>
> wrote:
>
> > kenneth mcfarland on dev@logging.apache.org replies:
> > Why don't you call close() or commit() on the indexwriter? If log4j2
> is
> > serious about being an auditing platform some attention to flushing
> and
> > such should be addressed. Note I am not an expert but I believe I am
> > somewhere in the ballpark.
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/apache/logging-log4j2/pull/82#
> issuecomment-317618689>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/ABIfN6D_
> jsLHaJif7ngIlu4q1HLTGYJdks5sRWFQgaJpZM4Ns1oB>
> > .
> >
>
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Re: Type Erasure

[kenneth mcfarland]

That's really cool and I apologize for being ignorant. I did Google
afterwards, it reminds me of the first time I saw a ternary. Thanks for the
explanation.



On Jul 24, 2017 8:25 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote:

> In Java 7, the Java compiler can use type inference to allow you to change
> the verbose:
>
> List list = new ArrayList();
>
> into the less verbose:
>
> List list = new ArrayList<>();
>
> Since you are assigning to a List, the only type you can possibly
> use in an ArrayList<> is a String, so you can omit it.
>
> Gary
>
> On Mon, Jul 24, 2017 at 5:20 PM, kenneth mcfarland <
> kennethpmcfarl...@gmail.com> wrote:
>
> > I have a simple question as why there is generic arrays like new
> > ArrayList<>(); in classes like:
> >
> > log4j-core/src.../core/builder/impl/DefaultComponentBuilder();
> >
> > Note, this is not a "why didn't you do it differently" question, I am
> > asking so I can learn from you. Thx.
> >
> > Kenneth
> >
>

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

[kenneth mcfarland]

Why don't you call close() or commit() on the indexwriter? If log4j2 is
serious about being an auditing platform some attention to flushing and
such should be addressed. Note I am not an expert but I believe I am
somewhere in the ballpark.

On Mon, Jul 24, 2017 at 8:27 PM, garydgregory  wrote:

> Github user garydgregory commented on the issue:
>
> https://github.com/apache/logging-log4j2/pull/82
>
> Thank you for your submission @liyuj ! Can you try the "Lucene5"
> branch and confirm that it works for you?
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Type Erasure

[kenneth mcfarland]

I have a simple question as why there is generic arrays like new
ArrayList<>(); in classes like:

log4j-core/src.../core/builder/impl/DefaultComponentBuilder();

Note, this is not a "why didn't you do it differently" question, I am
asking so I can learn from you. Thx.

Kenneth

Re: Log4J2 user guide

[kenneth mcfarland]

If this <http://logging.apache.org/log4j/2.0/log4j-users-guide.pdf> is it
then, its just silly things like the bullet formatting consistency on page
2 (not roman numeral, the actual page 2). I just figured if I was reading
through it I might as well clean up what I find as I go like the commenting
stuff lately.

On Sun, Jul 23, 2017 at 6:24 PM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:

> The link to the pdf is on the main log4j 2 web page. The pdf is generated
> from the same source used to generate the html pages and we rarely review
> the pdf to see that things have extended beyond the page borders, so it
> wouldn’t be surprising to see those kinds of errors.  The only changes in
> the pdf will be the same changes that have gone into the web site.  I don’t
> believe we publish a snapshot of the site anywhere so you would have to run
> it locally. Instructions for doing that are on the wiki.
>
> Ralph
>
> > On Jul 23, 2017, at 5:08 PM, kenneth mcfarland <
> kennethpmcfarl...@gmail.com> wrote:
> >
> > The reason I ask is because there are multiple versions showing up on
> > Google and the version I downloaded and have been reading is for 2.8 (I
> > believe) with some prominent formatting errors.
> >
> > As I have been getting up to speed I have been contributing simple fixes
> > for documentation and the like, and I've found some errors in the PDF
> guide
> > but what is the point fixing an out of date guide ya know?
> >
> > Thank you Gary :)
> >
> >
> > On Jul 23, 2017 4:53 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote:
> >
> >> Good question, I do not see it on the site. You might have to build it
> from
> >> sources but I do not see instructions in our BUILDING.md file on how to
> use
> >> maven-pdf-plugin.
> >>
> >> Gary
> >>
> >> On Sun, Jul 23, 2017 at 4:04 PM, kenneth mcfarland <
> >> kennethpmcfarl...@gmail.com> wrote:
> >>
> >>> Can somebody point me at the newest version of the log4j2 user guide
> PDF
> >>> file?
> >>>
> >>
>
>
>

Re: Log4J2 user guide

[kenneth mcfarland]

The reason I ask is because there are multiple versions showing up on
Google and the version I downloaded and have been reading is for 2.8 (I
believe) with some prominent formatting errors.

As I have been getting up to speed I have been contributing simple fixes
for documentation and the like, and I've found some errors in the PDF guide
but what is the point fixing an out of date guide ya know?

Thank you Gary :)


On Jul 23, 2017 4:53 PM, "Gary Gregory" <garydgreg...@gmail.com> wrote:

> Good question, I do not see it on the site. You might have to build it from
> sources but I do not see instructions in our BUILDING.md file on how to use
> maven-pdf-plugin.
>
> Gary
>
> On Sun, Jul 23, 2017 at 4:04 PM, kenneth mcfarland <
> kennethpmcfarl...@gmail.com> wrote:
>
> > Can somebody point me at the newest version of the log4j2 user guide PDF
> > file?
> >
>

Log4J2 user guide

[kenneth mcfarland]

Can somebody point me at the newest version of the log4j2 user guide PDF
file?

Re: [GitHub] logging-log4j2 issue #96: Remove empty comments and fix default buffer size ...

[kenneth mcfarland]

I noticed you created a JIRA for the 8012 buf size defualt. Is this
something I should do when I'm doing something more than a typo fix?

Thank you 

On Jul 21, 2017 2:16 PM, "kenneth mcfarland" <kennethpmcfarl...@gmail.com>
wrote:

> Sure will, new to git sorry. Still figuring it out.
>
> On Jul 21, 2017 2:14 PM, "garydgregory" <g...@git.apache.org> wrote:
>
>> Github user garydgregory commented on the issue:
>>
>> https://github.com/apache/logging-log4j2/pull/96
>>
>> Thank you for your patch but I've already applied
>> https://github.com/apache/logging-log4j2/pull/95 Can you merge and
>> resubmit SVP?
>>
>>
>> ---
>> If your project is set up for it, you can reply to this email and have
>> your
>> reply appear on GitHub as well. If your project does not have this feature
>> enabled and wishes so, or if the feature is enabled but not working,
>> please
>> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
>> with INFRA.
>> ---
>>
>

Re: Log4j 2 build hangs

[kenneth mcfarland]

Confirming on El Capitan.

On Jul 15, 2017 9:38 AM, "Mikael Ståldal"  wrote:

> This test works on Java 7, but fails on Java 8 and Java 9:
>
> [ERROR] Failures:
> [ERROR] RollingAppenderDirectWriteWithReconfigureTest.testRollingFil
> eAppenderWithReconfigure:68
> Expected: is <2>
>  but: was <1>
>
>
>
> On 2017-07-14 08:22, Ralph Goers wrote:
>
>> It turns out this test will have to be skipped on MacOS as there is no
>> native FileWatcher service and instead it resorts to polling. Because of
>> this it is missing all of the events and it hangs.
>>
>> Ralph
>>
>> On Jul 13, 2017, at 6:06 PM, Ralph Goers 
>>> wrote:
>>>
>>> In my case I can see that the test is looking for files in
>>> target/rolling-tmp. I have a bunch of compressed files in rolling2 but no
>>> files in rolling-tmp
>>>
>>> Ralph
>>>
>>> On Jul 13, 2017, at 1:24 PM, Mikael Ståldal  wrote:

 For me it doesn't hand, but a test fail:

 [ERROR] Failures:
 [ERROR] RollingAppenderDirectWriteWithReconfigureTest.testRollingFil
 eAppenderWithReconfigure:68
 Expected: is <2>
 but: was <1>



 On 2017-07-13 19:27, Ralph Goers wrote:

> I have tried to run the build twice and it has hung both times in a
> new test with the stack trace below. Can someone take a look? The history
> says it was recently created by Pierrick and committed by Gary.
> Ralph
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x0007aeb009c0> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.Loc
> kSupport.park(LockSupport.java:175)
> at java.util.concurrent.locks.Abs
> tractQueuedSynchronizer$ConditionObject.await(AbstractQueued
> Synchronizer.java:2039)
> at java.util.concurrent.LinkedBlo
> ckingDeque.takeFirst(LinkedBlockingDeque.java:492)
> at java.util.concurrent.LinkedBlo
> ckingDeque.take(LinkedBlockingDeque.java:680)
> at sun.nio.fs.AbstractWatchService.take(AbstractWatchService.
> java:118)
> at org.apache.logging.log4j.core.
> appender.rolling.RollingAppenderTempCompressedFilePatternTes
> t.testAppender(RollingAppenderTempCompressedFilePatternTest.java:136)
>



>>>
>>>
>>>
>>
>>
>

Re: Maven Dependency Resolution Error

[kenneth mcfarland]

Issue resolved itself when running mvn clean install from logging-log4j
root, weird but good.. thank you 

On Jul 12, 2017 4:42 PM, "kenneth mcfarland" <kennethpmcfarl...@gmail.com>
wrote:

> Originally I did skip the tests, but upon trying again without
> -Dmaven.test.skip=true the error is still present :(
>
> kenobi@ubuntu:~/git/logging-log4j2/log4j-core-its$ mvn clean install
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache Log4j Core Integration Tests 2.9-SNAPSHOT
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.854 s
> [INFO] Finished at: 2017-07-12T16:40:05-07:00
> [INFO] Final Memory: 11M/110M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project log4j-core-its: Could not
> resolve dependencies for project org.apache.logging.log4j:
> log4j-core-its:pom:2.9-SNAPSHOT: Failure to find org.apache.logging.log4j:
> log4j-core:jar:tests:2.9-SNAPSHOT in https://repository.apache.org/
> snapshots was cached in the local repository, resolution will not be
> reattempted until the update interval of apache.snapshots has elapsed or
> updates are forced -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> DependencyResolutionException
>
>
> On Wed, Jul 12, 2017 at 3:44 PM, Ralph Goers <ralph.go...@dslextreme.com>
> wrote:
>
>> Did you skip tests in your build? This shouldn’t happen if you run mvn
>> clean install.
>>
>> Ralph
>>
>> > On Jul 12, 2017, at 1:49 PM, kenneth mcfarland <
>> kennethpmcfarl...@gmail.com> wrote:
>> >
>> > Maven is having some issues when I try to build. >.<
>> >
>> > [ERROR] Failed to execute goal on project log4j-core-its: Could not
>> resolve
>> > dependencies for project
>> > org.apache.logging.log4j:log4j-core-its:pom:2.9-SNAPSHOT: Failure to
>> find
>> > org.apache.logging.log4j:log4j-core:jar:tests:2.9-SNAPSHOT in
>> > https://repository.apache.org/snapshots was cached in the local
>> repository,
>> > resolution will not be reattempted until the update interval of
>> > apache.snapshots has elapsed or updates are forced -> [Help 1]
>>
>>
>>
>

Re: Maven Dependency Resolution Error

[kenneth mcfarland]

Originally I did skip the tests, but upon trying again without
-Dmaven.test.skip=true the error is still present :(

kenobi@ubuntu:~/git/logging-log4j2/log4j-core-its$ mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO]

[INFO] Building Apache Log4j Core Integration Tests 2.9-SNAPSHOT
[INFO]

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 0.854 s
[INFO] Finished at: 2017-07-12T16:40:05-07:00
[INFO] Final Memory: 11M/110M
[INFO]

[ERROR] Failed to execute goal on project log4j-core-its: Could not resolve
dependencies for project
org.apache.logging.log4j:log4j-core-its:pom:2.9-SNAPSHOT: Failure to find
org.apache.logging.log4j:log4j-core:jar:tests:2.9-SNAPSHOT in
https://repository.apache.org/snapshots was cached in the local repository,
resolution will not be reattempted until the update interval of
apache.snapshots has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException


On Wed, Jul 12, 2017 at 3:44 PM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:

> Did you skip tests in your build? This shouldn’t happen if you run mvn
> clean install.
>
> Ralph
>
> > On Jul 12, 2017, at 1:49 PM, kenneth mcfarland <
> kennethpmcfarl...@gmail.com> wrote:
> >
> > Maven is having some issues when I try to build. >.<
> >
> > [ERROR] Failed to execute goal on project log4j-core-its: Could not
> resolve
> > dependencies for project
> > org.apache.logging.log4j:log4j-core-its:pom:2.9-SNAPSHOT: Failure to
> find
> > org.apache.logging.log4j:log4j-core:jar:tests:2.9-SNAPSHOT in
> > https://repository.apache.org/snapshots was cached in the local
> repository,
> > resolution will not be reattempted until the update interval of
> > apache.snapshots has elapsed or updates are forced -> [Help 1]
>
>
>

Maven Dependency Resolution Error

[kenneth mcfarland]

 Maven is having some issues when I try to build. >.<

[ERROR] Failed to execute goal on project log4j-core-its: Could not resolve
dependencies for project
org.apache.logging.log4j:log4j-core-its:pom:2.9-SNAPSHOT: Failure to find
org.apache.logging.log4j:log4j-core:jar:tests:2.9-SNAPSHOT in
https://repository.apache.org/snapshots was cached in the local repository,
resolution will not be reattempted until the update interval of
apache.snapshots has elapsed or updates are forced -> [Help 1]

Re: (Fixed) Building with Java 9

[kenneth mcfarland]

I used used this command to try:
sudo apt-get install openjdk-9-jdk
It does have javac but the javac included does not support the --release
flag and fails to build. I do however believe it has all the jdk tools.


On Jul 11, 2017 10:43 PM, "Ralph Goers" <ralph.go...@dslextreme.com> wrote:

> 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 <
> kennethpmcfarl...@gmail.com> wrote:
> >
> > 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 install on the latest Ubuntu.
> >
> > Only after installing and configuring the oracle version of the jdk-9
> early
> > access will builds of the log4j2-api-java9 build correctly.
> >
> > After discovering the --release flag is a new feature to java 9 I able to
> > hunt down the problem. I'd like to save others the frustration of my
> > experience. Thanks to Matt and Ralph and others who offered their help
> and
> > expertise in helping me track down a fix.
> >
> > Kenneth
>
>
>

(Fixed) Building with Java 9

[kenneth mcfarland]

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 install on the latest Ubuntu.

Only after installing and configuring the oracle version of the jdk-9 early
access will builds of the log4j2-api-java9 build correctly.

After discovering the --release flag is a new feature to java 9 I able to
hunt down the problem. I'd like to save others the frustration of my
experience. Thanks to Matt and Ralph and others who offered their help and
expertise in helping me track down a fix.

Kenneth

Re: Log4J2-API-Java9 Build Failure

[kenneth mcfarland]

 AM, Apache <ralph.go...@dslextreme.com> wrote:

> 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 <
> kennethpmcfarl...@gmail.com> wrote:
> >
> > I am running Ubuntu 16.04.2 LTS AMD 64
> >
> > The sole purpose of my laptop is to get this build to work. I've
> literally
> > reformatted my machine just for this project and I'm at my wits end
> trying
> > to figure this out after googling for 2 days.
> >
> > I've made sure the POM reflects the correct path to my jdk, and I've
> > experimented the oracle early release jdk, openjdk 9. I made the
> > toolchains.xml file point t the correct java 9 paths.
> >
> > If it doesn't complain about not finding JDK=9, then it fails on this:
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile
> > (default-compile) on project log4j-api-java9: Compilation failure
> > [ERROR] javac: invalid flag: --release
> > [ERROR] Usage: javac  
> > [ERROR] use -help for a list of possible options
> >
> > Other modules in the trunk build fine, but I want them all to build the
> way
> > they should. Any advice would be greatly apprecaited!
> >
> > Kenneth
>
>
>

Log4J2-API-Java9 Build Failure

[kenneth mcfarland]

I am running Ubuntu 16.04.2 LTS AMD 64

The sole purpose of my laptop is to get this build to work. I've literally
reformatted my machine just for this project and I'm at my wits end trying
to figure this out after googling for 2 days.

I've made sure the POM reflects the correct path to my jdk, and I've
experimented the oracle early release jdk, openjdk 9. I made the
toolchains.xml file point t the correct java 9 paths.

If it doesn't complain about not finding JDK=9, then it fails on this:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile
(default-compile) on project log4j-api-java9: Compilation failure
[ERROR] javac: invalid flag: --release
[ERROR] Usage: javac  
[ERROR] use -help for a list of possible options

Other modules in the trunk build fine, but I want them all to build the way
they should. Any advice would be greatly apprecaited!

Kenneth

Mentor Support Log4J2

[Kenneth Mcfarland]

I would like to help contribute, is there anyone out there that can help a
newbie? I've helped correct some things in the cms webpage but I would like
to get experience doing more than correcting typos. Can someone shadow me?
Thanks in advance!

kennethpaulmcfarl...@gmail.com