losed and marked as a duplicate.
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same config works fine)
> ---
>
> Key: LOG4NET-493
>
ried it and it works fine.
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same config works fine)
> ---
>
> Key: LOG4NET-493
>
nditional compilation symbols too to get it to work
from visual studio. If you don't want to do that you'll have to build it with
nant.
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
&g
[
https://issues.apache.org/jira/browse/LOG4NET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Vanicky updated LOG4NET-493:
-
Comment: was deleted
(was: I will check it and let you know.)
> Log4net 1.2.14/ADO.
from trunk to .NET 3.5? Changing project's target
framework to .NET 3.5 generates some compile-errors.
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same co
know.
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same config works fine)
> ---
>
> Key: LOG4NET-493
> URL: https://
great if you could verify if the issue is indeed
fixed in the latest trunk. Would you volunteer to check that?
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same co
fast reaction!
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same config works fine)
> ---
>
> Key: LOG4NET-493
> URL: htt
This looks like a duplicate and is already fixed in trunk. A fix will be
released soon, apologies for the inconvenience. If you need the fix right now
please build log4net from source.
> Log4net 1.2.14/ADO.NET appender throws exception when starting (1.2.13 with
> same config work
[
https://issues.apache.org/jira/browse/LOG4NET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Vanicky updated LOG4NET-493:
-
Attachment: Log4NetDebugViewLog.LOG
Log4netConfig.xml
> Log4net 1.2
[
https://issues.apache.org/jira/browse/LOG4NET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Vanicky updated LOG4NET-493:
-
Attachment: (was: Log4netConfig.xml)
> Log4net 1.2.14/ADO.NET appender thr
[
https://issues.apache.org/jira/browse/LOG4NET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Vanicky updated LOG4NET-493:
-
Attachment: (was: Log4NetDebugViewLog.LOG)
> Log4net 1.2.14/ADO.NET appender thr
[
https://issues.apache.org/jira/browse/LOG4NET-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miroslav Vanicky updated LOG4NET-493:
-
Attachment: Log4NetDebugViewLog.LOG
Log4netConfig.xml
> Log4net 1.2
Miroslav Vanicky created LOG4NET-493:
Summary: Log4net 1.2.14/ADO.NET appender throws exception when
starting (1.2.13 with same config works fine)
Key: LOG4NET-493
URL: https://issues.apache.org/jira/browse
On 2015-11-11, Jeremiah Gowdy wrote:
> I don't know if we have yet figured out a change to the relationship
> with the nuget package maintainer, although I'm encouraged that some
> communication was happening there.
I vaguely recall Domink said he was in contact, but may be wrong
entirely. So fa
Hi,
thanks for the Kudos, we're happy to help! Let's hope that the latest
release satisfies your needs and does not introduce the need for more
changes. ;-)
Cheers
On 2015-11-11 15:40, Jeremiah Gowdy wrote:
Thank you so much to everyone who put time in to make this release happen.
These a
Thank you so much to everyone who put time in to make this release happen.
These async/await context fixes will really help us.
I don't know if we have yet figured out a change to the relationship with the
nuget package maintainer, although I'm encouraged that some communication was
happening
As Alexander Houben pointed out the download link has been wrong, the
correct link is
http://logging.apache.org/log4net/download_log4net.cgi
On 2015-11-11, Stefan Bodewig wrote:
> The Apache log4net team is pleased to announce the release of Apache
> log4net 1.2.14. The rele
On 2015-11-11, Alexander Houben wrote:
> Hi Stefan,
> the link http://logging.apache.org/log4net/download.html gives me a 404!
> Did you mean http://logging.apache.org/log4net/download_log4net.cgi ?
You are correct.
Stefan
; The Apache log4net team is pleased to announce the release of Apache
> log4net 1.2.14. The release is available for download at
>
> http://logging.apache.org/log4net/download.html
>
> The Apache log4net library is a tool to help the programmer output log
> statements to a varie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Apache log4net team is pleased to announce the release of Apache
log4net 1.2.14. The release is available for download at
http://logging.apache.org/log4net/download.html
The Apache log4net library is a tool to help the programmer output
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With binding +1s by
Dominik Psenner
Ralph Goers
Stefan Bodewig
and additional +1s by
Jeremiah Gowdy
Gert Driesen
the vote has passed. I'll proceed with publishing the artifcats and
giving the mirrors a bit of time to catch up before announcing the
Replying again to include Log4NET Dev
+1
I tried to build one of the sample apps but they seem to require .Net 1.0 and
.Net 4.0 only seems to go down to 2.0. So I really can’t verify that it runs.
But all the packaging seems to be fine.
Ralph
> On Nov 10, 2015, at 4:50 AM, Stefan Bodewig wr
On 2015-11-10, Ivan Habunek wrote:
> I can jump in if nobody else is available,
Thanks
> but I must warn you that I don't have a good idea how to test the
> release. Do you have any guidelines?
About the same way I'd test a log4php release :-)
Seriously, if you haven't got a .NET project using
I can jump in if nobody else is available, but I must warn you that I don't
have a good idea how to test the release. Do you have any guidelines?
Regards,
Ivan
On 10 November 2015 at 08:42, Stefan Bodewig wrote:
> On 2015-11-10, Jeremiah Gowdy wrote:
>
> > How many do we need to get this releas
On 2015-11-10, Jeremiah Gowdy wrote:
> How many do we need to get this release approved?
At least three +1s by PMC members and more +1s than -1s.
Stefan
How many do we need to get this release approved?
> On Nov 9, 2015, at 9:02 PM, Stefan Bodewig wrote:
>
> Making my own +1 explicit
>
> Right now we've got two PMC members voting +1 and two non-binding +1s by
> community members.
>
>> This vote will closes no sooner than in 72 hours, 1630 GMT
Making my own +1 explicit
Right now we've got two PMC members voting +1 and two non-binding +1s by
community members.
> This vote will closes no sooner than in 72 hours, 1630 GMT
> 10-Nov 2015
About 10 more hours ...
Stefan
On 2015-11-09, Dominik Psenner wrote:
> These files however should be discussed:
> log4net.snk.readme
> tests/lib/prerequisites.txt
> These two should contain a small license header.
IMHO, these are small text files without anything anybody would consider
IP.
They have been skipped by prev
Fixing the rat report post-release is ok with me. There are differences
to the last release:
These are fine by me because they are generated files:
src/GeneratedAssemblyInfo.cs
bin/mono/4.0/release/log4net.xml
bin/mono/4.0/oldkey/log4net.xml
bin/mono/4.0/debug/log4net.xml
bin/mono/2.0/
On 2015-11-09, Dominik Psenner wrote:
> Good catch, Ralph. On past releases I used the RAT report to check if
> there are differences and if there were differences I doublechecked if
> they were OK or not. But somehow the "Project Reports" link has gone
> missing:
> https://logging.apache.org/log
Gary
Stefan
On 2015-11-08, Gary Gregory wrote:
> Pardon my NAnt newbness:
> LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
> NANTEXE_PATH is nant.exe
> BUILD_FILE is E:\temp\rc\log4net-1.2.14\log4net.build
> log4net:ERROR XmlConfiguratorAttribute: Exceptio
e the release? I do not have any Net apps to
test...
Gary
>
>
> Stefan
>
> On 2015-11-08, Gary Gregory wrote:
>
> > Pardon my NAnt newbness:
>
> > LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
> > NANTEXE_PATH is nant.exe
> > BUILD_FILE is E:\temp\rc\l
zip.png
Stefan
On 2015-11-08, Gary Gregory wrote:
> Pardon my NAnt newbness:
> LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
> NANTEXE_PATH is nant.exe
> BUILD_FILE is E:\temp\rc\log4net-1.2.14\log4net.build
> log4net:ERROR XmlConfiguratorAttribute: Exception getting
> Configura
Pardon my NAnt newbness:
LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
NANTEXE_PATH is nant.exe
BUILD_FILE is E:\temp\rc\log4net-1.2.14\log4net.build
log4net:ERROR XmlConfiguratorAttribute: Exception getting
ConfigurationFileLocation. Must be able to resolve
ConfigurationFileLocation when ConfigFile
>>
>> But i had and wont have the time to check and test the binaries.
>> On 7 Nov 2015 5:32 p.m., "Stefan Bodewig" wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> log4net 1.2.14 RC2 is available for review
+1
Van: Stefan Bodewig
Verzonden: zaterdag 7 november 2015 17:32
Aan: log4net-dev@logging.apache.org, gene...@logging.apache.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
log4net 1.2.14 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/logging
On 2015-11-08, Jeremiah Gowdy wrote:
> Sorry, I mean
> +1
yes is fine as well :-)
Thanks a lot
Stefan
Sorry, I mean
+1
> On Nov 7, 2015, at 8:32 AM, Stefan Bodewig wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> log4net 1.2.14 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/logging/log4net
>(revision 11058)
>
> D
I vote yes.
> On Nov 7, 2015, at 8:32 AM, Stefan Bodewig wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> log4net 1.2.14 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/logging/log4net
>(revision 11058)
>
> Details
So what are you basing your vote on?
Gary
On Nov 7, 2015 11:00 AM, "Dominik Psenner" wrote:
> +1
>
> But i had and wont have the time to check and test the binaries.
> On 7 Nov 2015 5:32 p.m., "Stefan Bodewig" wrote:
>
>> -BEGIN PGP SIGNED MESSAG
+1
But i had and wont have the time to check and test the binaries.
On 7 Nov 2015 5:32 p.m., "Stefan Bodewig" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> log4net 1.2.14 RC2 is available for review here:
> https://dist.apache.org/repos/dist/dev/loggin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
log4net 1.2.14 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/logging/log4net
(revision 11058)
Details of changes since 1.2.14 are in the release notes:
http://people.apache.org/~bodewig/log4net/site/release/release
On 2015-11-02, Ralph Goers wrote:
> I apologize Stefan. I had every intention on reviewing the release but time
> just got away from me. I will look at the next one for sure.
Thanks a lot, Ralph. I plan to cut a new release candidate at the
coming weekend.
Cheers
Stefan
On 2015-11-01, Dominik Psenner wrote:
> There were a few things I wanted to be fixed and I'm finished with doing so
> right now. Should we start another release vote if the next jenkins build
> is ok?
Given that it takes several hours to build an RC I won't be able to do
so before the coming week
I apologize Stefan. I had every intention on reviewing the release but time
just got away from me. I will look at the next one for sure.
Ralph
> On Nov 1, 2015, at 10:00 PM, Stefan Bodewig wrote:
>
> This vote has failed to attract enough votes but there is hope a new RC
> will attract more
This vote has failed to attract enough votes but there is hope a new RC
will attract more votes (at least one more vote).
Stefan
There were a few things I wanted to be fixed and I'm finished with doing so
right now. Should we start another release vote if the next jenkins build
is ok? Despite that I've another question regarding the website. As
mentioned before the menu on the pages:
* https://logging.apache.org/log4net/mai
iew the
> release. Then we might start a new vote and see how it goes. Read you soon.
> On 21 Oct 2015 4:54 p.m., "Jeremiah Gowdy" wrote:
>>> 1 Release these artifacts
>>> On Oct 17, 2015, at 11:20 PM, Stefan Bodewig wrote:
>>> log4net 1.2.14 RC1 is a
rote:
> +1 Release these artifacts
>
> > On Oct 17, 2015, at 11:20 PM, Stefan Bodewig wrote:
> >
> > log4net 1.2.14 RC1 is available for review here:
> > https://dist.apache.org/repos/dist/dev/logging/log4net
> > (revision 10847)
> >
>
+1 Release these artifacts
> On Oct 17, 2015, at 11:20 PM, Stefan Bodewig wrote:
>
> log4net 1.2.14 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/logging/log4net
> (revision 10847)
>
> Details of changes since 1.2.13 are in the r
On 2015-10-18, Stefan Bodewig wrote:
> Votes, please. This vote will close in 72 hours, not before 0700 GMT
> 21-Oct 2015
Well, I haven't seen any formal vote at all, and even counting my own
implicit one, this isn't enough.
The concerns raised against the site have been addressed, I hope, I've
On 2015-10-19, Gary Gregory wrote:
> Hm, something is missing with my set up running "build.cmd compile-all":
welcome to .NET development on Windows :-)
http://stefan.samaflost.de/blog/en/Apache/Log4Net/working_on_the_1.2.11_release.html
you'll need to make sure Windows doesn't consider your NA
On 2015-10-19, wrote:
> Hi,
> Stefan Bodewig wrote on 19.10.2015 13:40:28:
>> [...]
>> If you know of any tool that creates static HTML documentation, then we
>> I'll be happy zo run it once manually to update the site and figure out
>> how to add it to the build process later.
>> For XMLUnit.
Hi,
Stefan Bodewig wrote on 19.10.2015 13:40:28:
> [...]
> If you know of any tool that creates static HTML documentation, then we
> I'll be happy zo run it once manually to update the site and figure out
> how to add it to the build process later.
>
> For XMLUnit.NET I've switched to monodoc bu
Hey Gary,
is E: a network share?
On 2015-10-19 14:40, Gary Gregory wrote:
Hm, something is missing with my set up running "build.cmd compile-all":
LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
NANTEXE_PATH is nant.exe
BUILD_FILE is E:\temp\rc\log4net-1.2.14\log4net.build
log
Hm, something is missing with my set up running "build.cmd compile-all":
LOG4NET_DIR is E:\temp\rc\log4net-1.2.14
NANTEXE_PATH is nant.exe
BUILD_FILE is E:\temp\rc\log4net-1.2.14\log4net.build
log4net:ERROR XmlConfiguratorAttribute: Exception getting
ConfigurationFileLocation. Must
On 2015-10-19, Dominik Psenner wrote:
> On 2015-10-19 06:00, Stefan Bodewig wrote:
>> On 2015-10-18, Dominik Psenner wrote:
>>> The website has the following issues:
>>> * Sdk reference is a chm file, no longer a http website
>> This won't change, I'm afraid.
>> I forgot to mention it, sorry. n
On 2015-10-19, Ralph Goers wrote:
> There was a security notice that was sent to all PMCs about a month
> ago. The cgi is no longer to be used.
unless it only wraps "mirrors.cgi", which we do.
Cheers
Stefan
On 2015-10-19 06:00, Stefan Bodewig wrote:
On 2015-10-18, Dominik Psenner wrote:
The website has the following issues:
* Sdk reference is a chm file, no longer a http website
This won't change, I'm afraid.
I forgot to mention it, sorry. ndoc has finally reached the point where
it doesn't w
There was a security notice that was sent to all PMCs about a month ago. The
cgi is no longer to be used.
Ralph
> On Oct 18, 2015, at 9:02 PM, Stefan Bodewig wrote:
>
>> On 2015-10-18, Ralph Goers wrote:
>>
>> The download cgi extension should be changed to lua.
>
> Really, I don't recall se
On 2015-10-18, Ralph Goers wrote:
> The download cgi extension should be changed to lua.
Really, I don't recall seeing such a request. Our script is a simple
wrapper around the mirrors.cgi script, which is supposed to still work
IIRC. At least it still does here
http://logging.apache.or
On 2015-10-18, Dominik Psenner wrote:
> The website has the following issues:
> * Sdk reference is a chm file, no longer a http website
This won't change, I'm afraid.
I forgot to mention it, sorry. ndoc has finally reached the point where
it doesn't work for out codebase anymore, it just dies
The download cgi extension should be changed to lua.
Sent from my iPhone
> On Oct 18, 2015, at 12:28 PM, Dominik Psenner wrote:
>
> The website has the following issues:
>
> * Sdk reference is a chm file, no longer a http website
> * several pages have missing menu items in the project documen
The website has the following issues:
* Sdk reference is a chm file, no longer a http website
* several pages have missing menu items in the project documentation section
* on sites where the missing project documentations are shown, they are
displayed with an indent and the menu therefore looks a
On 2015-10-18, Gary Gregory wrote:
> I've never built this guy before. Do you have a BUILDING.txt or
> instructions on a Wiki on how to validate an log4net RC?
http://logging.apache.org/log4net/release/building.html
Forget all the Visual Studio stuff and go to "NAnt". You should use
NAnt 0.92,
I've never built this guy before. Do you have a BUILDING.txt or
instructions on a Wiki on how to validate an log4net RC?
Gary
On Sat, Oct 17, 2015 at 11:20 PM, Stefan Bodewig wrote:
> log4net 1.2.14 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/logg
log4net 1.2.14 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/logging/log4net
(revision 10847)
Details of changes since 1.2.13 are in the release notes:
http://people.apache.org/~bodewig/log4net/site/release/release-notes.html
The tag is here:
https
On 2015-08-18, Thomas Clegg wrote:
> The diff is located
> here[https://gist.github.com/twcclegg/2a931390eaf95d9367c9] and is
> also attached.
I've manually merged all changes made to trunk after log4net 1.2.13 that
didn't break BWC to the 1.2.x branch and would want to cut 1.2.14 from
there. I'
On 2015-08-18, Jeremiah Gowdy wrote:
> My colleague Thomas Clegg and I are proposing to do a release of
> log4net numbered 1.2.14. This release would be the existing 1.2.13
> release, plus the two patches for LOG4NET-455 and LOG4NET-462.
> According to our testing, this fixes log4net’s thread con
My colleague Thomas Clegg and I are proposing to do a release of log4net
numbered 1.2.14. This release would be the existing 1.2.13 release, plus the
two patches for LOG4NET-455 and LOG4NET-462. According to our testing, this
fixes log4net’s thread context for async/await usage. By doing a bu
71 matches
Mail list logo
