) which gets a little redundant.
On Fri, Jan 31, 2020 at 23:15 Ralph Goers
wrote:
> Gitbox and GitHub are interchangeable. I have yet to make a commit to
> Gitbox.
>
> Ralph
>
> > On Jan 31, 2020, at 9:22 AM, Matt Sicker wrote:
> >
> > Also, when it comes to rel
ScalaDoc links need to be updated with the proper location.
* The ScalaDocs all need to be aggregated (again?) to ensure they're
all on the site.
--
Matt Sicker
ging/log4j/scala/
> Nexus does its own old fashioned thing with MD5s...
>
> Gary
>
>
> > +1
> >
> > Ralph
> >
> > > On Feb 1, 2020, at 3:38 PM, Matt Sicker wrote:
> > >
> > > This is a vote to release Log4j Scala API 12.0-rc1. Th
body mind reminding me why do we need multiple JDKs for build
> rather than just sticking to 11 and tuning the target version whenever
> necessary?
>
> Kind regards.
>
--
Matt Sicker
2-2771
> > [2] https://issues.apache.org/jira/browse/LOG4J2-2764
> >
> > On Tue, Feb 4, 2020 at 2:24 PM Matt Sicker wrote:
> > >
> > > There are some compile errors if you try to use 11 for everything. If
> > those
> > > are fixed, we can like
14:14, Gary Gregory wrote:
>
> Matt,
>
> If have Kotlin specific instructions I am happy to test those.
>
> Gary
>
> On Sat, Feb 1, 2020, 14:56 Matt Sicker wrote:
>
> > Hi all,
> >
> > I’ll be attempting to start release processes for both the Scala
I might be able to do that in parallel, yeah. Let's see what Ralph's
plans are, though, as I recall him mentioning he wanted to make a
release sometime as well.
On Thu, 6 Feb 2020 at 10:53, Gary Gregory wrote:
>
> On Thu, Feb 6, 2020 at 10:45 AM Matt Sicker wrote:
>
> >
ry
>
> On Sat, Feb 1, 2020 at 5:38 PM Matt Sicker wrote:
>
> > This is a vote to release Log4j Scala API 12.0-rc1. This vote will
> > remain open for at least 72 hours and requires 3 +1 votes and more +1
> > than -1 votes.
> >
> > Highlights:
> > *
2.12.3.
LOG4J2-2115::: Update Log4j dependency from 2.8.1 to 2.9.1.
LOG4J2-2116::: Update log4j-api-scala_2.12 from Scala 2.12.3 to 2.12.4.
--
Matt Sicker
down'. Or. is my
> understanding erroneous?
>
> Gary
>
> On Sat, Feb 8, 2020 at 3:01 PM Matt Sicker wrote:
>
> > Hello all, this is a vote to release the second release candidate of
> > Log4j Scala API 12.0. This vote will remain open for at least 72 hours
&
I see that log4j2 artifacts use the rcN suffix in the element of
the parent pom, so it seems that I may have tagged this in the wrong
order. I'll update the release process instructions.
On Sun, 9 Feb 2020 at 11:44, Matt Sicker wrote:
>
> I don’t think we’ve copied our tags over to
anism to employ a certain Function
> method for injection?
>
> Kind regards.
>
--
Matt Sicker
formed a merge? I can’t
> imagine a real person has that id.
>
> Ralph
--
Matt Sicker
then manually create a tag from the -rcn tag.
> Unfortunately, I don’t always remember to do that.
>
> Ralph
>
> > On Feb 9, 2020, at 11:36 AM, Matt Sicker wrote:
> >
> > I see that log4j2 artifacts use the rcN suffix in the element of
> > the parent pom, so
e is configured properly in the first place. It seems
> that Jenkins seems to be building only Java applications, while APR
> and other C applications seem to be built on ci.apache.org. What's
> the best way to help with this?
>
> -Robert Middleton
>
--
Matt Sicker
esults back out while
> also installing the proper dependencies.
>
> -Robert Middleton
>
> On Wed, Feb 19, 2020 at 6:53 PM Matt Sicker wrote:
> >
> > Some of the Jenkins nodes have Docker available which makes building
> > simpler here.
> >
> > On Wed, Feb
de parameters which can also utilize
dependency injection
* Fits more naturally with the SPI as written so far
--
Matt Sicker
🎉
On Sun, 23 Feb 2020 at 13:06, Apache Jenkins Server
wrote:
>
> See
> <https://builds.apache.org/job/Log4j2Windows/62/display/redirect?page=changes>
>
--
Matt Sicker
, Ralph Goers wrote:
>
> Although I see what you are doing in the test it isn’t clear to me what
> impact it will have on Log4j and plugins. I am looking forward to seeing
> examples of that.
>
> Ralph
>
> > On Feb 23, 2020, at 1:22 PM, Matt Sicker wrote:
> >
>
o vaguely talk about it.
GitHub diff page:
https://github.com/apache/logging-log4j2/compare/mean-bean-machine
On Sun, 23 Feb 2020 at 15:11, Matt Sicker wrote:
>
> One of the more noticeable impacts it will have is the ability to
> define all the various singleton objects and configurati
x27;ll point to [1] where these runners can get far more
complicated.
[1]:
https://github.com/spring-projects/spring-framework/blob/master/spring-test/src/main/java/org/springframework/test/context/junit4/SpringJUnit4ClassRunner.java
On Sun, 23 Feb 2020 at 17:54, Matt Sicker wrote:
>
> I
quot;git checkout
> > tags/log4j-2.13.1-rc1”
> > b) for an existing working copy to “git pull” and then “git checkout
> > tags/log4j-2.13.1-rc1”
> >
>
> Or just "git clone https://github.com/apache/logging-log4j2.git -b
> log4j-2.13.1-rc1"
>
> Gary
>
>
> >
> > Web Site: http://rgoers.github.io/log4j2-site/index.html.
> >
> > Maven Artifacts:
> > https://repository.apache.org/content/repositories/orgapachelogging-1053
> >
> > Distribution archives:
> > https://dist.apache.org/repos/dist/dev/logging/log4j/
> >
> > You may download all the Maven artifacts by executing:
> > wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> > https://repository.apache.org/content/repositories/orgapachelogging-1053/org/apache/logging/log4j/
> >
> > Ralph
> >
--
Matt Sicker
“git pull” and then “git checkout
> tags/log4j-2.13.1-rc2”
>
> Web Site: http://rgoers.github.io/log4j2-site/index.html.
>
> Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachelogging-1055
>
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> https://repository.apache.org/content/repositories/orgapachelogging-1055/org/apache/logging/log4j/
>
> Ralph
--
Matt Sicker
2, Ralph Goers wrote:
>
> Yes, our web site is very large. It isn’t required that we distribute it but
> I always like to.
>
> That test failure is not something I have encountered nor seen in the Jenkins
> builds.
>
> Ralph
>
> > On Feb 26, 2020, at 10:
False alarm; turns out it was only failing while connected to VPN.
Tests pass when using a normal network.
On Wed, 26 Feb 2020 at 11:46, Matt Sicker wrote:
>
> System info:
>
> openjdk version "1.8.0_222"
> OpenJDK Runtime Environment (Zulu 8.40.0.25-CA-macosx) (build 1.
* Signatures good
* Builds and tests pass
* Site looks good
+1
On Wed, 26 Feb 2020 at 13:38, Matt Sicker wrote:
>
> False alarm; turns out it was only failing while connected to VPN.
> Tests pass when using a normal network.
>
> On Wed, 26 Feb 2020 at 11:46, Matt Sicker wrote:
.withgoogle.com/
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
--
Matt Sicker
of a start? There are 219 Improvement or New Feature
> issues in Jira to pick from besides these.
>
> Ralph
>
>
>
> > On Feb 28, 2020, at 7:49 AM, Matt Sicker wrote:
> >
> > Given some project ideas from the community here, I might be able to help
&
I remember seeing test failures around daylight saving time sometimes.
This year has a leap day, so I wonder if that works properly?
--
Matt Sicker
gt; Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme http://www.AM-SoFT.de/
>
> Telefon...05151- 9468- 55
> Fax...05151- 9468- 88
> Mobil..0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
--
Matt Sicker
ords, I've discussed this issue with the colleagues at
> > work, where we use LogstashLayout with its excessive payload
> > prevention mechanisms in tens of thousands of services, they really
> > would like to have either it or a replacement, FYI.
> >
> > I am pretty much lost at this stage. Any thoughts?
> >
> > Kinds regards.
> >
>
--
Matt Sicker
Considering we’re on track to log4j 3.0 this year, that could certainly
make for a talk on its own. Based on the various tracks available this
year, is anyone planning to submit a talk or have any suggestions on topics
they’d like to see?
--
Matt Sicker
dson.maven.MavenEmbedder.(MavenEmbedder.java:110)
> at hudson.maven.MavenEmbedder.(MavenEmbedder.java:137)
> at hudson.maven.MavenUtil.createEmbedder(MavenUtil.java:211)
> at
> hudson.maven.RedeployPublisher.createEmbedder(RedeployPublisher.java:292)
> at
> hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:155)
> at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
> at
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
> at hudson.model.Run.execute(Run.java:1840)
> at
> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
> at
> hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
>
> 176 errors
> at
> com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1025)
> at
> org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
> at
> org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263)
> ... 19 more
> [INFO] Deployment failed after 5.3 sec
> Build step 'Deploy artifacts to Maven repository' changed build result to
> FAILURE
>
--
Matt Sicker
Event, the output of a compressed binary layout
> > > can be considered okay while its JSON representation might appear
> > > excessive. But I've just aforementioned filtering should kick in
> > > before layout. Sort of a chicken and egg problem.
> > >
> > > For the records, I've discussed this issue with the colleagues at
> > > work, where we use LogstashLayout with its excessive payload
> > > prevention mechanisms in tens of thousands of services, they really
> > > would like to have either it or a replacement, FYI.
> > >
> > > I am pretty much lost at this stage. Any thoughts?
> > >
> > > Kinds regards.
> > >
>
--
Matt Sicker
ut needs
> work as the GelfLayout should be unnecessary. Of course SyslogLayout and
> RFC5424Layout are useful if you are logging to syslog and neither has any
> dependencies so they belong in core.
>
> There is such a thing as making things too fine grained. It isn’t very user
> friendly to have to include 10 jars just to do some simple logging. At the
> same time, it is no fun to have to manually exclude dependencies that
> shouldn’t be required.
>
> Ralph
>
>
--
Matt Sicker
on how to implement a dependency-free JSON parser?
> >
> > Not really. I am not sure avoiding the use of a JSON parser library just
> > to include the JsonTemplateLayout in core is worth the effort. People who
> > want to use JSON aren’t going to mind bringing in a JSON library. And if it
> > means adding a JSON parser to core that we have to maintain, unless it is
> > just a couple of classes I don’t know that I would want to do that.
> >
> > Ralph
> >
> >
> >
--
Matt Sicker
I almost forgot that I noted an idea last year to do a State of Logging
Services type of presentation considering there were a few others like that
accepted then. Such a talk could touch on all our components.
On Tue, Mar 3, 2020 at 08:17 Matt Sicker wrote:
> Considering we’re on track to lo
with Log4j 2.
>
> As you mentioned a talk on 3.0 might be worth having but that would only
> make sense if a 3.0 release was imminent.
>
> Ralph
>
> > On Mar 4, 2020, at 11:44 AM, Matt Sicker wrote:
> >
> > I almost forgot that I noted an idea last year t
> > > ...
> > > [ERROR] Failed to execute goal on project log4j-plugins: Could not
> > > resolve dependencies for project
> > > org.apache.logging.log4j:log4j-plugins:jar:3.0.0-SNAPSHOT: Could not
> > > find artifact org.apache.logging.log4j:log4j-api:jar:tests:3.0.0-SNAPSHOT
> > >
> > > I have checked Travis[1] and Jenkins[2], their end doesn't look bright
> > > either.
> > >
> > > How do you people deal with this? How do you develop? Which branch
> > > shall I use to base JsonTemplateLayout?
> > >
> > > Kind regards.
> > >
> > > [1] https://travis-ci.org/apache/logging-log4j2/builds
> > > [2] https://builds.apache.org/view/L/view/Logging/
> > >
> >
> >
--
Matt Sicker
t; started
> >>> that with LogBuilder by creating a directory named “internal” off of
> core.
> >>> Rather than having internal directories all over the place I am
> thinking we
> >>> should mimic the same existing package structure under the internal
> >>> directory and move private classes there.
> >>>
> >>> Thoughts?
> >>>
> >>> Ralph
> >>>
>
>
> --
Matt Sicker
extreme.com>
> > > > wrote:
> > > >
> > > > > Did you specify a charset on the layout that supports that
> character?
> > > > >
> > > > > Ralph
> > > > >
> > > > > > On Mar 10, 2020, at 1:57 PM, Christopher
> > > wrote:
> > > > > >
> > > > > > I tried to put in a kitty (🐈) in my LayoutPattern, but it didn't
> > > > > > work. It replaced it with some weird character. Is this is a
> known
> > > > > > bug?
> > > > > > Does PatternLayout not support wide characters?
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > > -ck
> > >
> >
>
--
Matt Sicker
11:19 AM, Ralph Goers
> wrote:
> >>
> >> Is anyone else having problems with TimeFilterTest in core today? I
> am in Arizona so we did not spring forward as we are MST all year. I see
> the test is setting a timezone of America/Los Angeles.
> >>
> >> Ralph
> >
> >
> >
>
>
> --
Matt Sicker
l should be to
> make them simple for users to integrate.
> > >
> > > As for benchmarks, if you have current benchmarks then include them.
> They don’t have to be updated with each release but the page should
> indicate what release they were for.
> > >
> > > Speaking of documentation, if you are creating a separate page or
> pages for JsonTemplateLayout make sure there is an entry in the general
> Layout page that has a general description and a link to the full
> documentation.
> > >
> > > Ralph
> > >
> > >
> > >
> >
> >
>
--
Matt Sicker
`log4j3`
> property prefix?
>
> Kinds regards.
>
> [1]
> https://github.com/vy/log4j2/blob/json-template-layout/log4j-layout-json-template/src/main/java/org/apache/logging/log4j/layout/json/template/JsonTemplateLayoutDefaults.java
--
Matt Sicker
Whoops, typo there. The normalized form is log4j2.fooBarBaz. Note the
dot after the 2.
On Thu, 12 Mar 2020 at 15:56, Matt Sicker wrote:
>
> They all get normalized into camelCasePropertyNames without the
> leading log4j, log4j2, or even org.apache.logging.log4j, or Log4j, or
> re
Oh, and see also the docs written in this section:
https://logging.apache.org/log4j/2.x/manual/configuration.html#SystemProperties
On Thu, 12 Mar 2020 at 15:57, Matt Sicker wrote:
>
> Whoops, typo there. The normalized form is log4j2.fooBarBaz. Note the
> dot after the 2.
>
> On T
], their end doesn't look bright
> either.
> >
> > How do you people deal with this? How do you develop? Which branch
> > shall I use to base JsonTemplateLayout?
> >
> > Kind regards.
> >
> > [1] https://travis-ci.org/apache/logging-log4j2/builds
> > [2] https://builds.apache.org/view/L/view/Logging/
>
--
Matt Sicker
ear none of which has had any
> >>> comments. There are 7 open PRs from 2019. There are currently 34 open
> >> pull
> >>> requests and no pull requests have been merged since October 2018.
> >>>
> >>> The only PMC members or committers who have recently worked on Log4net
> >>> indicated some time ago that they would no longer be able to work on
> the
> >>> project.
> >>>
> >>> We would appreciate any thoughts on this before we hold a vote to
> retire
> >>> the project.
> >>>
> >>> Ralph
> >>>
> >>
>
>
> --
Matt Sicker
d be of great help. It is a pretty large commit.
> >
> > Ralph
> >
> >> On Mar 29, 2020, at 2:19 PM, Gary Gregory
> wrote:
> >>
> >> Hi All:
> >>
> >> I see a current burst of activity on the commit list. I have not looked
> >> closely. Can anyone provide a big picture of what is happening?
> >>
> >> Thank you,
> >> Gary
> >
> >
> >
>
>
> --
Matt Sicker
b site to include Log4Net in a list of dormant projects
> > along with a description of what being dormant means.
> > 5. Mark all LOG4NET issues as wont fix in Jira.
> > 6. Ask INFRA to prevent new LOG4NET issues from being created.
> >
> > This vote will be open for 72 hours.
> >
> > Ralph
> >
>
--
Matt Sicker
All:
>
> I just had a case where I had two appenders with the same name in my XML
> config.
>
> Would it make sense to issue a WARN event to the status logger in this
> case?
>
> Gary
>
--
Matt Sicker
y over the Jenkinsfile to release-2.x
after confirming it works properly with master. I'm working on getting
the various reports generated into Jenkins as well.
For testing PRs, we can continue to use Travis (or GitHub Actions) to
avoid capacity issues on Jenkins.
--
Matt Sicker
Small update: the URL can also be accessed directly through the job
name rather than via the view:
https://builds.apache.org/job/log4j/
Easy URL to remember, too. ;)
On Fri, 3 Apr 2020 at 20:28, Matt Sicker wrote:
>
> I've deleted some old pipelines in Jenkins and am updating
So this looks like a real test failure. It's not happening in the
Windows agents, but it's happening in the Ubuntu agents.
On Sat, 4 Apr 2020 at 00:35, Apache Jenkins Server
wrote:
>
> See <https://builds.apache.org/job/Log4j%202%202.x/4160/display/redirect>
>
--
Matt Sicker
know what your preferences are for notification emails
so I can add it to the Jenkinsfile.
On Fri, 3 Apr 2020 at 21:30, Matt Sicker wrote:
>
> Small update: the URL can also be accessed directly through the job
> name rather than via the view:
>
> https://builds.apache.org/j
language support for macros
and a stronger runtime type system). This could also form a nice basis
for a collection of easy first-timer issues to clean up and get new
contributors!
On Sat, 4 Apr 2020 at 02:31, Matt Sicker wrote:
>
> I've copied the Jenkinsfile over to release-2.x. I&
h the "unstable"
build results are only being sent to Slack for now). Once I've
confirmed it's working in master, I'll backport the updates to
release-2.x again to finish this.
On Sat, 4 Apr 2020 at 12:46, Matt Sicker wrote:
>
> I almost forgot: I still need to re-ena
t code, or perform
> +releases. Although it is possible volunteers might choose to
> +participate in the future, it is best to assume there will be not
> +future development or releases.
> What is Apache log4net™
>
>
>
>
--
Matt Sicker
Seems like a bug in the config. I don’t think a DOAP file or a Jira report
needs to be generated for every module in the project. That seems to add a
lot of network calls which takes a bit of time.
On Sun, Apr 5, 2020 at 00:36 Ralph Goers wrote:
>
>
> > On Apr 4, 2020, at 10:46 AM,
urce, zipped it and then published it to
> > > > https://dist.apache.org/repos/dist/dev/logging/log4net/ <
> > > > https://dist.apache.org/repos/dist/dev/logging/log4net/>.
> > > >
> > > > This is a vote to move those artifacts to the distribution release
> > > > directory.
> > > >
> > > > This vote will remain open for 72 hours.
> > > >
> > > > Ralph
> > >
> >
>
> -ck
--
Matt Sicker
gt; domain, if that's agreeable to everyone and the project retains it's
> >>>>>>> original branding and status. One thing I'm concerned about here is
> >>>>>>> the
> >>>>>>> dormant backlog
> >>>>>>> 2. As above, with a bit of a clean-slate philosophy: I'd like to
> >>>>>>> remove
> >>>>>> all
> >>>>>>> backlog items that aren't critical and start with the least
> >>>>>>> outstanding
> >>>>>>> stuff possible. If a report is important, it will be reported again.
> >>>>>> Trying
> >>>>>>> to trace down the authors and origins of 2+year-old reports is going
> >>>>>>> to
> >>>>>> be
> >>>>>>> frustrating. Issues which aren't attended to just become noise in the
> >>>>>>> backlog, imo.
> >>>>>>> 3. I fork and perform the "clean slate" approach of above, inviting
> >>>>>> others
> >>>>>>> to use my variant and log issues there. Uptake will naturally be slow
> >>>>>>> (if
> >>>>>>> even noticeable), which will give me time to deal with incoming
> >>>>>>> issues.
> >>>>>> On
> >>>>>>> the other hand, I'd have full control and no need to bother anyone
> >>>>>>> else.
> >>>>>> I
> >>>>>>> would have to come up with a new name and make it clear that it's a
> >>>>>>> fork,
> >>>>>>> though also make it clear I'd be standing on the shoulders of giants.
> >>>>>>> Personally, I'd like (1) because it keeps the project that people
> >>>>>>> rely on
> >>>>>>> alive. Since I'm new to the mailing list, I can't discern yet the
> >>>>>> sentiment
> >>>>>>> towards the project, except that everyone was quite happy to have it
> >>>>>>> made
> >>>>>>> dormant, so it feels like there's not a lot of desire to keep it
> >>>>>>> going --
> >>>>>>> which is ok: everything comes to an end at some point, and, as stated
> >>>>>>> earlier, I'm sure there are good reasons for making log4net dormant.
> >>>>>>> As a
> >>>>>>> consumer of log4net, I'd much rather not have to switch over to
> >>>>>>> another
> >>>>>>> framework once there's an issue which affects me more than my logged
> >>>>>>> one
> >>>>>>> (inability to flush logs -- it was on a proof-of-concept project, so
> >>>>>>> it
> >>>>>>> isn't _that_ important to have the functionality right now).
> >>>>>>> Apologies for the rambling message. I was prompted to reach out by
> >>>>>>> Ralph
> >>>>>>> Goers in the discussion for LOG4NET-606, so I hope I haven't been a
> >>>>>> bother.
> >>>>>>> -d
> >>>>>>> --
> >>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >>>>>>> If you say that getting the money is the most important thing
> >>>>>>> You will spend your life completely wasting your time
> >>>>>>> You will be doing things you don't like doing
> >>>>>>> In order to go on living
> >>>>>>> That is, to go on doing things you don't like doing
> >>>>>>> Which is stupid.
> >>>>>>> - Alan Watts
> >>>>>>> https://www.youtube.com/watch?v=-gXTZM_uPMY
> >>>>>>> *Quidquid latine dictum sit, altum sonatur. *
> >>
> >>
> >
> >
> >
>
>
--
Matt Sicker
r? Should I
> create a PR using the build system (npm / node-based) that I use for my
> projects? I'm happy to do so.
>
> -d
> On 2020-04-07 17:39:31, Matt Sicker wrote:
> We mostly develop on the JVM which has a fairly different build
> system. Performing a release for t
ld
> > I create a PR using the build system (npm / node-based) that I use for my
> > projects? I'm happy to do so.
> >
> > -d
> > On 2020-04-07 17:39:31, Matt Sicker wrote:
> > We mostly develop on the JVM which has a fairly different build
> > system
aven.apache.org/plugins/maven-compiler-plugin/multirelease.html
[2]: https://github.com/meterware/multirelease-parent/blob/master/pom.xml
--
Matt Sicker
apache.org/job/log4j/job/release-2.x/10/console
> > Changes: https://builds.apache.org/job/log4j/job/release-2.x/10/changes
> >
> > --
> > Mr. Jenkins
>
>
> --
Matt Sicker
failure in log4j/release-2.x.
>
> Build: https://builds.apache.org/job/log4j/job/release-2.x/14/
> Logs: https://builds.apache.org/job/log4j/job/release-2.x/14/console
> Changes: https://builds.apache.org/job/log4j/job/release-2.x/14/changes
>
> --
> Mr. Jenkins
--
Matt Sicker
.org/job/log4j/job/release-2.x/15/console
> Changes: https://builds.apache.org/job/log4j/job/release-2.x/15/changes
>
> --
> Mr. Jenkins
> Director of Continuous Integration
--
Matt Sicker
Updated, see build #15 for the latest failure.
On Sat, 11 Apr 2020 at 18:37, Matt Sicker wrote:
>
> Oh I see the issue here. Needs more back ports from master. I’ll update this.
>
> On Sat, Apr 11, 2020 at 18:25 Ralph Goers wrote:
>>
>> Why have these builds been fail
at the
> CI server (ie, learn enough docker to be dangerous)
> - raise a PR
>
> -d
--
Matt Sicker
/log4j/job/release-2.x/19/console
> Changes: https://builds.apache.org/job/log4j/job/release-2.x/19/changes
>
> --
> Mr. Jenkins
> Director of Continuous Integration
--
Matt Sicker
console
> > Changes: https://builds.apache.org/job/log4j/job/master/47/changes
> >
> > --
> > Mr. Jenkins
> > Director of Continuous Integration
>
>
--
Matt Sicker
.apache.org/job/log4j/job/master/49/
> Logs: https://builds.apache.org/job/log4j/job/master/49/console
> Changes: https://builds.apache.org/job/log4j/job/master/49/changes
>
> --
> Mr. Jenkins
> Director of Continuous Integration
--
Matt Sicker
a 9+).
On Tue, 14 Apr 2020 at 16:41, Matt Sicker wrote:
>
> This is supposed to be working. Let me retry the build. The previous
> errors were sometimes related to timeouts due to too much build
> activity on builds.a.o.
>
> On Tue, 14 Apr 2020 at 15:47, Ralph Goers wrote:
>
t was:<""[\u008E]"">
>17) [c=143 (escapeJson)] expected:<""[?]""> but was:<""[\u008F]"">
>18) [c=144 (escapeJson)] expected:<""[?]""> but was:<""[\u0090]"">
>19) [c=145 (escapeJson)] expected:<""[?]""> but was:<""[\u0091]"">
>20) [c=146 (escapeJson)] expected:<""[?]""> but was:<""[\u0092]"">
>21) [c=147 (escapeJson)] expected:<""[?]""> but was:<""[\u0093]"">
>22) [c=148 (escapeJson)] expected:<""[?]""> but was:<""[\u0094]"">
>23) [c=149 (escapeJson)] expected:<""[?]""> but was:<""[\u0095]"">
>24) [c=150 (escapeJson)] expected:<""[?]""> but was:<""[\u0096]"">
>25) [c=151 (escapeJson)] expected:<""[?]""> but was:<""[\u0097]"">
>26) [c=152 (escapeJson)] expected:<""[?]""> but was:<""[\u0098]"">
>27) [c=153 (escapeJson)] expected:<""[?]""> but was:<""[\u0099]"">
>28) [c=154 (escapeJson)] expected:<""[?]""> but was:<""[\u009A]"">
>29) [c=155 (escapeJson)] expected:<""[?]""> but was:<""[\u009B]"">
>30) [c=156 (escapeJson)] expected:<""[?]""> but was:<""[\u009C]"">
>31) [c=157 (escapeJson)] expected:<""[?]""> but was:<""[\u009D]"">
>32) [c=158 (escapeJson)] expected:<""[?]""> but was:<""[\u009E]"">
>33) [c=159 (escapeJson)] expected:<""[?]""> but was:<""[\u009F]"">
>
>I am not a JSON expert, but I find this worrying. Would anybody
>provide some further feedback on what is going on here, please?
>
> Kind regards.
--
Matt Sicker
inform me if this is a bug and if it is, how can I report it?
>
> Thank you,
> Daniel
--
Matt Sicker
t; >
> > Build: https://builds.apache.org/job/log4j/job/master/53/
> > Logs: https://builds.apache.org/job/log4j/job/master/53/console
> > Changes: https://builds.apache.org/job/log4j/job/master/53/changes
> >
> > --
> > Mr. Jenkins
> > Director of Continuous Integration
>
>
--
Matt Sicker
I'll work on writing up some documentation about how this pipeline
works over the weekend.
On Fri, 17 Apr 2020 at 13:02, Matt Sicker wrote:
>
> This test has been flaky on Jenkins. I used the simplest pipeline
> possible here. If these failures are specific to a particular Jenkin
ad finished.
>
> Ralph
>
> > On Apr 17, 2020, at 11:02 AM, Matt Sicker wrote:
> >
> > This test has been flaky on Jenkins. I used the simplest pipeline
> > possible here. If these failures are specific to a particular Jenkins
> > node, then that might be somethin
Oh, and the build finished because I added the "-fae" (fail at end)
maven flag so we could get a full test report each time rather than an
abbreviated one.
On Fri, 17 Apr 2020 at 16:10, Matt Sicker wrote:
>
> https://builds.apache.org/job/log4j/job/master/53/testReport/
>
>
at 16:19, Matt Sicker wrote:
>
> Oh, and the build finished because I added the "-fae" (fail at end)
> maven flag so we could get a full test report each time rather than an
> abbreviated one.
>
> On Fri, 17 Apr 2020 at 16:10, Matt Sicker wrote:
> >
> >
I've cleaned up the jenkinsfiles, added links to various things, and
started a wiki page where I can free-form describe anything else that
might be relevant. I also removed a couple things that weren't really
relevant.
On Fri, 17 Apr 2020 at 16:45, Matt Sicker wrote:
>
> Note t
using the term Apache-2.0,
> as
> >>> per the url it was pointing to
> >>> - have updated to point at the same feather.png the package
> >>> used to point to online, renamed within the project to
> package-icon.png for
> >>> clarity
> >>>
> >>> Next up:
> >>> dotnet core tooling wants sdks for net20 and net35 to be installed on
> the
> >>> host. Alternatively, we could install all of Build Tools 2019 on the
> host.
> >>> I think the former might be neater. At any rate, I now have to figure
> out
> >>> enough docker to be dangerous and get a standalone build environment
> up and
> >>> running.
> >>>
> >>> -d
> >>
> >>
> >
> > --
> > Dominik Psenner
>
>
> --
Matt Sicker
t results:
> https://builds.apache.org/job/log4j/job/release-2.x/28/testReport/
> Changes: https://builds.apache.org/job/log4j/job/release-2.x/28/changes
>
> --
> Mr. Jenkins
> Director of Continuous Integration
>
--
Matt Sicker
lease does not contain the zip of the web site. SVN is
> > refusing to let me commit it, probably due to its size. It is not required
> > for a release.
> >
> > You may download all the Maven artifacts by executing:
> > wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> > https://repository.apache.org/content/repositories/orgapachelogging-1056/org/apache/logging/log4j/
> >
> > Ralph
> >
--
Matt Sicker
> > >
> > >
> > > Regards,
> > >
> > > Abdul Haseeb Hussain
> > >
> > >
> > > --
> > >
> > >
> > > *The information in this email is confidential and solely for the use of
> > the intended recipient(s). If you receive this email in error, please
> > notify the sender and delete the email from your system immediately. In
> > such circumstances, you must not make any use of the email or its contents.
> > Views expressed by an individual in this email do not necessarily reflect
> > the views of Matillion Ltd.
> > >
> > > *
> > >
> > > *Matillion Ltd accepts no responsibility for any damage caused by
> > malicious software transmitted by email. Email transmission cannot be
> > guaranteed to be secure and error free, it is possible for it to be
> > intercepted, lost, destroyed, later, incomplete or with added malware. The
> > sender does not accept liability for any errors or omissions in the
> > contents of this message, which arise as a result of email transmission
> > >
> > > *
> > >
> > > *Matillion Ltd, Station House, Stamford New Road, Altrincham, England,
> > WA14 1EP (Main and registered office address). *_Company number: 07474948._
> > >
> >
> >
> >
>
> --
>
>
> *The information in this email is confidential and solely for the use of
> the intended recipient(s). If you receive this email in error, please
> notify the sender and delete the email from your system immediately. In
> such circumstances, you must not make any use of the email or its contents.
> Views expressed by an individual in this email do not necessarily reflect
> the views of Matillion Ltd.
>
> *
>
> *Matillion Ltd accepts no responsibility
> for any damage caused by malicious software transmitted by email. Email
> transmission cannot be guaranteed to be secure and error free, it is
> possible for it to be intercepted, lost, destroyed, later, incomplete or
> with added malware. The sender does not accept liability for any errors or
> omissions in the contents of this message, which arise as a result of email
> transmission
>
> *
>
> *Matillion Ltd, Station House, Stamford New Road,
> Altrincham, England, WA14 1EP (Main and registered office address).
> *_Company number: 07474948._
--
Matt Sicker
ncurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> > at java.lang.Thread.run(Thread.java:748)
> > DEBUG StatusLogger Using ShutdownCallbackRegistry class
> > org.apache.logging.log4j.core.util.DefaultShutdownCallbackRegistry
> > DEBUG StatusLogger Took 0.21
server dependency within my tomcat
> log4j2/lib folder
>
> On Thu, 23 Apr 2020 at 14:01, Matt Sicker wrote:
>
> > If you’re using log4j2 in a war file, you should add log4j-web as a
> > dependency.
> >
> > On Thu, Apr 23, 2020 at 05:57 Abdul Hussain
> > wrote:
Can you tell us more about how you assemble and deploy this application?
There multiple ways to integrate log4j2 into web apps.
On Thu, Apr 23, 2020 at 08:51 Abdul Hussain
wrote:
> without the web jar my web application does not output logs.
>
> On Thu, 23 Apr 2020 at 14:25, Matt Sick
ssues we are having, our integration with
> SLF4J log messages seem fine with preserving the thread context hence
> why we've decided to switch all our JUL logs to use SLF4J, would be
> good to find the root cause of that excption.
>
>
> On Thu, 23 Apr 2020 at 14:53, Matt S
Relevant links:
https://docs.oracle.com/javase/8/docs/api/java/util/logging/Filter.html
https://docs.oracle.com/javase/8/docs/api/java/util/logging/LogManager.html
On Thu, 23 Apr 2020 at 10:41, Matt Sicker wrote:
>
> It almost sounds like you have duplicate jars somewhere, or you may
://issues.apache.org/jira/browse/LOG4J2-2819
CVE Details:
CWE: 297
CVSS: 3.7 (Low) CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Affects: Apache Log4j <= 2.13.1
Fixed: Log4j 2.13.2
Reported by: Peter Stöckli
--
Matt Sicker
Secretary, Apache Software Foundation
VP Logging Services, ASF
host system is matters.
>
> Thanks
> -d
>
>
--
Matt Sicker
systems like circleci be acceptable too?
>
> -d
>
>
>
> On April 25, 2020 21:03:01 Matt Sicker wrote:
>
> > Info about our existing infra is documented here:
> > https://cwiki.apache.org/confluence/display/INFRA/Jenkins
> >
> > On Sat, 25 Apr 2020 at
-- I probably have
> 50 or 100 commits which are only attempts at getting TravisCI to build with
> varying approaches.
>
> -d
> On 2020-04-25 22:15:36, Matt Sicker wrote:
> The only external build systems that are set up for Apache right now
> are Travis and some limited G
Looks like AppVeyor is another option. Is that comparable to CircleCI?
(For context, I'm mostly familiar with Jenkins as I work on that
project at $dayjob)
On Mon, 27 Apr 2020 at 09:36, Matt Sicker wrote:
>
> Seems like I missed some other services:
> https://infra.apache.org
ent-sorcery
> > --
> > Sent from my phone. Typos are a kind gift to anyone who happens to find
> > them.
> >
> > On Mon, Apr 27, 2020, 16:48 Matt Sicker wrote:
> >
> >> Looks like AppVeyor is another option. Is that comparable to CircleCI?
> >>
&g
with Dockerfile's, github
> >> > actions or other build infrastructure. This [1] is a reference project
> >> that
> >> > works and may serve as a minimalistic sample that, to be honest, is pure
> >> > net core/netstandard and therefor
Further info:
https://issues.apache.org/jira/browse/INFRA-17133
https://issues.apache.org/jira/browse/INFRA-16927
https://issues.apache.org/jira/browse/INFRA-15964
https://issues.apache.org/jira/browse/INFRA-12197
On Mon, 27 Apr 2020 at 15:09, Matt Sicker wrote:
>
> According to past
ironment, which appears to be missing .net framework 3.5.
>
> -d
>
>
> On April 27, 2020 22:11:58 Matt Sicker wrote:
>
> > Further info:
> >
> > https://issues.apache.org/jira/browse/INFRA-17133
> > https://issues.apache.org/jira/browse/INFRA-16927
>
wing this, and I was
wondering if anyone else wanted to give feedback there later.
--
Matt Sicker
601 - 700 of 1881 matches
Mail list logo
