Re: logging-log4j2 git commit: LOG4J2-1748 and LOG4J2-1780 Remove ExecutorServices from LoggerContext

ving an > ExecutionService instead of ad hoc threads? > Item 4 - I just fixed this (see LOG4J2-1786 > <https://issues.apache.org/jira/browse/LOG4J2-1786>). > > > On Sun, Jan 15, 2017 at 11:26 AM, Apache <ralph.go...@dslextreme.com > <mailto:ral

Re: logging-log4j2 git commit: Convert index page to markdown

ndex.md b/src/site/markdown/index.md > new file mode 100644 > index 000..1adcb92 > --- /dev/null > +++ b/src/site/markdown/index.md > @@ -0,0 +1,124 @@ > + > + > +# Apache Log4j 2 > + > +Apache Log4j 2 is an upgrade to Log4j that provides significant improv

Re: Build failed in Jenkins: Log4jScala #1

mmon parent > pom for all log4j projects that can be used by log4j2, log4j-bom, > log4j-scala, and log4j-boot (and any others down the line). > > On 16 January 2017 at 14:07, Apache Jenkins Server <jenk...@builds.apache.org > <mailto:jenk...@builds.apache.org>> wrote: >

Re: ThreadContextMap3

I presume it was named ThreadContextMap3 so there could be a ThreadContextMap4 since 3 extends 2 and 2 extends the first one. Frankly, I dislike this practice very, very much. Instead, each interface should be named as you suggest and NOT extend the prior interface. Instead, the

Re: Remaining tasks for a 2.8 release

That will probably cover 80% of the use cases. Another option is to use a proxy factory that reads the file and determines if logger.rootLogger or logger.appender is present and routes to the Log4j1ConfigurationFactory if it is and the Log4j2 factory if it is not. Ralph > On Jan 18, 2017, at

Re: github

he comment from the outside. > > Accepting a PR is only a matter of merging the commits or using > something like "git am" on a file you create from the PR by appending > .patch - e.g. https://github.com/apache/logging-log4j2/pull/53.patch > > If you do so, this will no

Re: github

, and then you basically perform the merge yourself and push back to >> Apache's git repo. >> >> Really, the value of the GitHub side of things is mainly promotional. The >> pull request interface is a bit nicer than submitting patch files or .java >> file attachm

Re: Build failed in Jenkins: Log4jScala #1

> > On 16 January 2017 at 14:17, Matt Sicker <boa...@gmail.com > <mailto:boa...@gmail.com>> wrote: > I'd imagine it'd be pretty minimal, just inheriting from the latest ASF pom > and specifying some plugin baseline configurations where useful. > > On 16

Re: Experimenting with NIO

I tried using a FileChannel for the FileAppender a week or so ago to see if passing the ByteBuffer to the FileChannel would improve performance since it doesn’t have to be synchronized. I didn’t see any improvement though and I ended up reverting it. But I might have done something wrong.

Re: Roadmap for 2.8.1

e: >>>>> Why is the release of log4j-scala delayed? >>>>> >>>>> Ralph >>>>> >>>>>> On Feb 27, 2017, at 10:23 AM, Mikael Ståldal <mikael.stal...@magine.com> >>>>>> wrote: >>>>>> &g

Release Notes

Matt, I am wondering why you renamed RELEASE-NOTES.txt to RELEASE-NOTES.md? This file is generated by maven as part of preparing for the release. The output is a text file, not markdown. Furthermore, it caused the release to fail since it is included by name in the distribution zip files and

Re: ThreadContext.removeAll

Do you have a use case for it? In all my usages of the ThreadContext I always add attributes one at a time but then clear the whole ThreadContextMap at the end of the request. It isn’t clear to me why someone would want to remove a subset. Ralph > On Nov 10, 2016, at 5:55 AM, Mikael Ståldal

Java 9 StackTraceElement

Java 9’s StackTraceElement has been enhanced to include the module name and module version - http://download.java.net/java/jdk9/docs/api/java/lang/StackTraceElement.html#getModuleName . If I understand

Next release

I should have some time between Dec 24 through Jan 2 to perform the next release. If there are any critical bugs that need to be addressed please try to have them completed shortly after Christmas. Ralph - To unsubscribe,

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Running it again I obviously get a different host address but the same IP address is returned. Ralph > On Jan 9, 2017, at 7:20 PM, Apache <ralph.go...@dslextreme.com> wrote: > > Debugging this and InetAddress.getByName is returning an InetAddress object. > The value is >

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

It appears I need to use a different DNS server for it to stop redirecting me. I need to figure out which one to use. Ralph > On Jan 9, 2017, at 7:34 PM, Apache <ralph.go...@dslextreme.com> wrote: > > > Didn’t run the test. Don’t really have to. > > nslookup

Re: Log4j Boot

Please don’t try to match the Log4j version numbers. That would mean we would have to release them along with each Log4j release, which probably won’t be necessary. I would make the first release -beta, unless you think the first 1.0 release will be where it needs to be. Ralph > On Jan 9,

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

-- > > > http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/4254e255/log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/convert/TypeConverters.java > --

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

> I suppose technically the first part of a UUID can be an IPv4 address encoded > in hex. I'll make a better invalid value. > > On 9 January 2017 at 20:20, Apache <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > Debugging this and InetAddress.ge

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

like 8.8.8.8 (Google) and 4.2.2.2 (Level3) for DNS. There's > also 75.75.75.75 which is Comcast (or 2001:558:feed::1 which is their IPv6 > version apparently). > > On 9 January 2017 at 20:39, Apache <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>&

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

..@gmail.com> wrote: > > Well technically a UUID can be a valid hostname itself besides being > interpreted as a hex-encoded IP address (if the rest of it gets chopped off). > I've updated the test to use a jumble of invalid hostname characters instead. > > On 9 Januar

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

oa...@gmail.com> wrote: > > Let me know if my updated test still causes issues. > > On 9 January 2017 at 20:30, Apache <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > I suspect this is my ISP at work. When I enter an invalid domain I

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

a better assert message. Let me > know if you're still having an issue with it. Is it a failure from IntelliJ > or Maven? > > On 9 January 2017 at 19:47, Apache <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > This commit appears to be fa

Re: [1/2] logging-log4j2 git commit: Fixed concurrency issue affecting all layouts except PatternLayout and GelfLayout, which caused scrambled output and exceptions when logging synchronously from mul

Starting LoggerContext[name=org.apache.logging.log4j.core.layout.ConcurrentLoggingWithJsonLayoutTest, org.apache.logging.log4j.core.LoggerContext@14acaea5] with configuration XmlConfiguration[location=/Users/rgoers/projects/apache/logging/log4j/log4j2/current/log4j-core/target/test-classes

Re: ExecutorService.shutdown

> On Jan 10, 2017, at 2:09 PM, Mikael Ståldal wrote: > > It seems like ExecutorService.shutdown invokes executorService.shutdown() > twice If timeout is 0. Is this correct? A) Do you mean ExecutorServices? I don’t see any code that calls shutdown() twice. I do see

Re: [1/2] logging-log4j2 git commit: Fixed concurrency issue affecting all layouts except PatternLayout and GelfLayout, which caused scrambled output and exceptions when logging synchronously from mul

from my iPhone > > On Jan 10, 2017, at 13:42, Apache <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: > >> ConcurrentLoggingWithJsonLayoutTest is failing for me. I don’t understand >> why. &

Re: Looking into 2.7 slower than 2.6

BTW - can you see if you can get Stephen to post his messages here instead of twitter? I find that link very hard to read. Ralph > On Dec 5, 2016, at 10:36 AM, Apache <ralph.go...@dslextreme.com> wrote: > > No, but I am wondering if it is due to the stuff Remko has been doing w

Re: Looking into 2.7 slower than 2.6

No, but I am wondering if it is due to the stuff Remko has been doing with reducing memory usage. Ralph > On Dec 5, 2016, at 9:20 AM, Gary Gregory wrote: > > FYI, someone is reporting that 2.7 is 10% slower than 2.6. > > Please see

Re: Podling Report Reminder - December 2016

Is anyone planning on writing a report? Ralph > On Dec 5, 2016, at 4:39 PM, johndam...@apache.org wrote: > > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > p

Re: category = "Core"

The “core” category has nothing to do with what Log4j package the plugins are in. Rather, it has to do with where they are used. For example any Appender or Filter would be a “Core” plugin. This is because the plugin manager resolves plugins by the group they fall into. If you find all the

Re: Modules for SQL and MOM/JMS

I don’t think each of those should be in a separate repository, but it would make sense to have a single repo with all of them as sub projects. We do need to determine how we are going to change the layout of the Log4j site to accommodate all of this as each repository will have its own Maven

Re: Finally figured out why tests were running slowly for me

> >> Maybe in the "building Log4j2 from source" page? > https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/build.xml.vm > > <https://github.com/apache/logging-log4j2/blob/master/src/site/xdoc/build.xml.vm> >> >> Sent from my iPhone >

Re: How about a log4j-starters sort of repository?

Go for it! Ralph > On Jan 8, 2017, at 1:44 PM, Matt Sicker wrote: > > Also, one neat aspect of this that I didn't think of at first is that as we > trim down log4j-core and the main logging-log4j2 repository, users won't need > to worry about changing dependencies down the

Re: [slf4j-dev] Lambda support in SLF4J

The only downside is that anyone who has an implementation of SLF4J will have to add the new methods in order to upgrade. Log4j 2 has supported lambdas for quite a while doing exactly what you are proposing here. Obviously the SLF4J Supplier and the Log4j 2 Supplier won’t know anything about

Re: Configuration DSLs and other config improvements

A) What happened to the work on integrating Log4j 1 configurations? I’d rather see that finished before moving on to something else. B) After adding script support to various components I’m leaning more in favor of providing script flexibility where it is needed rather than doing the whole

Re: [VOTE] Release log4net 2.0.6 based on RC1

I suggest you include the PMC in your vote thread. Ralph > On Dec 22, 2016, at 7:58 AM, Stefan Bodewig wrote: > > Making my own vote explicit > > On 2016-12-20, Stefan Bodewig wrote: > >> Votes, please. This vote will close in 72 hours, 1000 GMT 24-Dec 2016 > >> [X] +1

Re: Any opposition to requesting git->jira integration?

Fine by me. Ralph > On Jan 14, 2017, at 8:19 PM, Matt Sicker wrote: > > http://apache.org/dev/svngit2jira.html > > > Basically, this would work similarly to how the current GitHub integration > works where comments made on pull

Re: logging-log4j-boot git commit: Add log4j-boot-spring module

SNAPSHOT > + compile > + > + > + org.apache.logging.log4j.boot > + log4j-boot-compat > + 1.0-SNAPSHOT > + compile > + > + > + org.springframework.boot > + spring-boot &

Re: logging-log4j2 git commit: LOG4J2-1748 and LOG4J2-1780 Remove ExecutorServices from LoggerContext

og4j/core/config/Configurator.java | 4 +- > .../log4j/core/util/Log4jThreadFactory.java | 11 --- > .../nosql/appender/cassandra/CassandraRule.java | 2 +- > src/site/xdoc/manual/configuration.xml.vm | 4 +- > 10 files changed, 59 insertions(+), 134 deletions(-) >

Re: Slf4j & (legacy?) best practices

jects/spring-boot/pull/7992 > <https://github.com/spring-projects/spring-boot/pull/7992>> to address this. > I consider Configurator to be a more stable internal API than what they were > doing before. > > This does bring me to a separate question: would making a public API to d

Re: Jenkins and Maven 3.5.0

e: > > I was thinking of just using 3.5.0. > > Gary > >> On Apr 9, 2017 6:48 AM, "Apache" <ralph.go...@dslextreme.com> wrote: >> Why? There is no reason our build process has to support every maven >> release. >> >> Sent from my iPad &g

Re: Jenkins and Maven 3.5.0

Why? There is no reason our build process has to support every maven release. Sent from my iPad > On Apr 8, 2017, at 5:44 PM, Matt Sicker wrote: > > Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it make > sense to switch to it there? I know in theory

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

> On Mar 7, 2017, at 9:20 PM, Matt Sicker <boa...@gmail.com> wrote: > > I may be missing some mailing lists considering I just subscribed to half of > them less than five minutes ago. > > This is a vote to merge the various Apache Logging Services mailing lists. > The

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

> On Mar 7, 2017, at 9:20 PM, Matt Sicker <boa...@gmail.com> wrote: > > I may be missing some mailing lists considering I just subscribed to half of > them less than five minutes ago. > > This is a vote to merge the various Apache Logging Services mailing lists. > The

Re: [VOTE] Combine the project user and dev mailing lists into user@ and dev@

> On Mar 7, 2017, at 9:20 PM, Matt Sicker <boa...@gmail.com> wrote: > > I may be missing some mailing lists considering I just subscribed to half of > them less than five minutes ago. > > This is a vote to merge the various Apache Logging Services mailing lists. > The

Jenkins build is still unstable: Log4j 2.x #2956

See

Jenkins build is still unstable: Log4j 2.x #2960

See

Jenkins build is still unstable: Log4j 2.x #2959

See

Jenkins build is back to normal : Log4j 2.x #2989

See

Jenkins build became unstable: Log4j 2.x #2991

See

Build failed in Jenkins: Log4j 2.x #2987

-sources.jar> [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ log4j-core --- [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-core/target/log4j-core-2.9-SNAPSHOT.jar> to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/logging/log4j/lo

Build failed in Jenkins: Log4j 2.x #2988

core-2.9-SNAPSHOT.jar> to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/logging/log4j/log4j-core/2.9-SNAPSHOT/log4j-core-2.9-SNAPSHOT.jar [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-core/pom.xml> to /home/jenkins/jenkins-slave/maven-repositories

Jenkins build became unstable: Log4j 2.x #2993

See

Jenkins build became unstable: Log4j 2.x #2980

See

Jenkins build is unstable: Log4j 2.x #2969

See

Jenkins build is back to stable : Log4j 2.x #2970

See

Jenkins build is still unstable: Log4j 2.x #2974

See

Jenkins build became unstable: Log4j 2.x #2973

See

Jenkins build is still unstable: Log4j 2.x #2976

See

Jenkins build is still unstable: Log4j 2.x #2975

See

Jenkins build is still unstable: Log4j 2.x #2977

See

Jenkins build is back to stable : Log4j 2.x #2978

See

Jenkins build is back to stable : Log4j 2.x #2994

See

Build failed in Jenkins: Log4j 2.x #2874

See -- [...truncated 3.99 KB...] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at

Jenkins build is back to normal : Log4jScala #60

See

Build failed in Jenkins: Log4jScala #59

on: 2.12.0 [WARNING] Multiple versions of scala libraries detected! model contains 10 documentable templates <https://builds.apache.org/job/Log4jScala/ws/log4j-api-scala_2.12/src/main/scala/org/apache/logging/log4j/scala/Logger.scala>:59: warning: Variable user.getName undefined in comm

Build failed in Jenkins: Log4j 2.x #2902

/bin/java -Xmx2g -Xms256m -XX:MaxPermSize=256m -cp /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/conf/logging jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven

Build failed in Jenkins: Log4j 2.x #2906

j-web-2.9-SNAPSHOT-test-sources.jar> [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ log4j-web --- [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/target/log4j-web-2.9-SNAPSHOT.jar> to /home/jenkins/jenkins-slave/maven-repositories/0/

Build failed in Jenkins: log4net-trunk-tests #111

See -- Started by upstream project "log4net-trunk-build" build number 241 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building

Build failed in Jenkins: log4net-trunk-tests #110

See Changes: [dpsenner] builder-netstandard: attempt to run groupadd and useradd in the stage [dpsenner] Revert "builder-netstandard: attempt to run groupadd and useradd in the [dpsenner] build-netstandard:

Jenkins build is unstable: Log4j 2.x #2875

See

Jenkins build is back to normal : Log4j 2.x #2879

See

Jenkins build is still unstable: Log4j 2.x #2876

See

Build failed in Jenkins: Log4j 2.x #2877

See -- [...truncated 3.99 KB...] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) at

Build failed in Jenkins: log4net-trunk-tests #108

See Changes: [dpsenner] Jenkinsfile: run mono-2.0 tests and record test results [dpsenner] Jenkinsfile: fixed typo [dpsenner] Jenkinsfile: record git log -1 into the package [dpsenner] Tests: download and

Jenkins build is unstable: Log4j 2.x #2873

See

Build failed in Jenkins: Log4j 2.x #2904

enkins-slave/maven-repositories/0/org/apache/logging/log4j/log4j-web/2.9-SNAPSHOT/log4j-web-2.9-SNAPSHOT.jar [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/pom.xml> to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/logging/log4j/log4j-web/2.

Build failed in Jenkins: Log4j 2.x #2905

SHOT-test-sources.jar> [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ log4j-web --- [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/target/log4j-web-2.9-SNAPSHOT.jar> to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/loggi

Build failed in Jenkins: log4net-trunk-tests #113

See Changes: [dpsenner] builder-netstandard: attempt to pass in the uid and gid of jenkins as [dpsenner] Jenkinsfile: another attempt to set jenkins_uid and jenkins_gid [dpsenner] Jenkinsfile: yet another

Build failed in Jenkins: log4net-trunk-tests #120

See Changes: [dpsenner] (doc) Contributing: added a code of conduct section -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" #

Build failed in Jenkins: log4net-trunk-tests #121

See Changes: [dpsenner] Contributing: rewrote great parts of the document to reflect the current -- [...truncated 2.91 KB...] > git rev-parse

Build failed in Jenkins: log4net-trunk-tests #125

See Changes: [dpsenner] ReleaseInstructions: renamed file to hint that it is in markup format [dpsenner] ReleaseInstructions: refactored to markup format --

Build failed in Jenkins: log4net-trunk-tests #122

See Changes: [dpsenner] Contributing: fixed wording and phrasing in several places -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" #

Jenkins build is back to normal : log4net-trunk-tests #123

See

Build failed in Jenkins: Log4j 2.x #2910

SHOT-test-sources.jar> [INFO] [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ log4j-web --- [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/target/log4j-web-2.9-SNAPSHOT.jar> to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/logging/l

Build failed in Jenkins: Log4j 2.x #2909

s/jenkins-slave/maven-repositories/1/org/apache/logging/log4j/log4j-web/2.9-SNAPSHOT/log4j-web-2.9-SNAPSHOT.jar [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/pom.xml> to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/logging/log4j/log4j-web/2.9-SNAPSHOT

Build failed in Jenkins: Log4j 2.x #2911

enkins-slave/maven-repositories/1/org/apache/logging/log4j/log4j-web/2.9-SNAPSHOT/log4j-web-2.9-SNAPSHOT.jar [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/pom.xml> to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/logging/log4j/log4j-web/2.9-SNAPSHOT/log4j-we

Build failed in Jenkins: Log4j 2.x #2912

t/log4j-web-2.9-SNAPSHOT.jar> to /home/jenkins/jenkins-slave/maven-repositories/1/org/apache/logging/log4j/log4j-web/2.9-SNAPSHOT/log4j-web-2.9-SNAPSHOT.jar [INFO] Installing <https://builds.apache.org/job/Log4j%202.x/ws/log4j-web/pom.xml> to /home/jenkins/jenkins-slave/maven-repositories/1/

Jenkins build is unstable: Log4j 2.x #2916

See

Build failed in Jenkins: log4net-trunk-tests #118

See Changes: [dpsenner] (doc) Contributing: fixed the syntax typos on a few links -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" #

Build failed in Jenkins: log4net-trunk-tests #114

See Changes: [dpsenner] Contributing: reformatted to markup syntax -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git

Build failed in Jenkins: log4net-trunk-tests #115

See Changes: [dpsenner] Contributing: fixed whitespaces and typos -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git

Build failed in Jenkins: log4net-trunk-tests #117

See Changes: [dpsenner] (doc) Contributing: fixed markup syntax of unordered lists -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" #

Build failed in Jenkins: log4net-trunk-tests #129

See Changes: [dpsenner] Contributing: fixed last added link -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 > git

Build failed in Jenkins: log4net-trunk-tests #127

See Changes: [dpsenner] ReleaseInstructions: moved important remark section to the top -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}"

Build failed in Jenkins: log4net-trunk-tests #128

See Changes: [dpsenner] ReleaseInstructions: fixed a few code quotes [dpsenner] Contributing: added link to the continuous deployment pipeline -- [...truncated 2.91

Jenkins build is back to normal : log4net-trunk-build #259

See

Build failed in Jenkins: log4net-trunk-build #258

See Changes: [dpsenner] ReleaseInstructions: fixed a few code quotes -- [...truncated 1.57 KB...] Seen branch in repository origin/master Seen branch in repository

Build failed in Jenkins: log4net-trunk-tests #131

See Changes: [dpsenner] Contributing: the link struggling continues.. -- [...truncated 2.91 KB...] > git rev-parse "refs/tags/rc/1.2.11-RC1^{commit}" # timeout=10 >

Build failed in Jenkins: log4net-trunk-tests #132

See Changes: [dpsenner] Contributing: moved sections and improved the cd-pipeline section -- [...truncated 2.85 KB...] > git rev-parse

<    1   2   3   4   5   6   7   8   9   10   >