Things to do before the next release

2016-09-14 Thread Stefan Bodewig
Hi all right now I'm able to build .NET 2.0 up to 4.5 and .NET Core with a single invocation of NAnt on my Win7 VM. We'll see if I find a way to also include Mono there, alternatively I can - once again - jiggle with two different machines and use an older version of Mono on Linux. This is I volun

Informational Version (was Re: Things to do before the next release)

2016-09-14 Thread Stefan Bodewig
On 2016-09-14, Stefan Bodewig wrote: > * decide on the version. I propose to use 2.0.6.0 for the next release > for all artifacts and try getting the "informational version" right - > this is Dominik's second proposal in > https://lists.apache.org/thread.html/42a97e0190fde4d5c54700965624c3515

Re: Informational Version (was Re: Things to do before the next release)

2016-09-14 Thread Dominik Psenner
That does not work and you must set a second AssemblyInformationalVersionAttribute where only a string can be specified. It is something that can live along with the AssemblyVersionAttribute and specify additional information about the assembly. I generally use this approach to include git/hg c

Re: Informational Version (was Re: Things to do before the next release)

2016-09-14 Thread Stefan Bodewig
This is me setting the AssemblyInformationalVersionAttribute, I didn't touch the AssemblyVersionAttribute at all. See the note at the bottom of https://msdn.microsoft.com/en-us/library/51ket42z(v=vs.110).aspx , | Although you can specify any text, a warning message appears on | compilation if

Re: Informational Version (was Re: Things to do before the next release)

2016-09-14 Thread Stefan Bodewig
On 2016-09-14, Stefan Bodewig wrote: > so we could simply suppress the warning. done. Stefan

Re: Informational Version (was Re: Things to do before the next release)

2016-09-14 Thread Dominik Psenner
Misread, sorry. On 14 Sep 2016 5:49 p.m., "Stefan Bodewig" wrote: > On 2016-09-14, Stefan Bodewig wrote: > > > so we could simply suppress the warning. > > done. > > Stefan >

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

2016-09-14 Thread Apache Jenkins Server
See

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

2016-09-14 Thread Apache Jenkins Server
See -- [...truncated 777 lines...] AUsrc\Appender\IBulkAppender.cs AUsrc\Appender\RollingFileAppender.cs AUsrc\Appender\MemoryAppender.cs AUsrc\Appender\AspNetTraceAppende

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

2016-09-14 Thread Apache Jenkins Server
See -- Started by user bodewig [EnvInject] - Loading node environment variables. Building remotely on windows1 (Windows) in workspace Updating htt