[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788949#comment-13788949
]
Dominik Psenner commented on LOG4NET-383:
-
We have no plans for 4.5, but it will
[
https://issues.apache.org/jira/browse/LOG4NET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788949#comment-13788949
]
Dominik Psenner edited comment on LOG4NET-383 at 10/8/13 6:13 AM:
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe updated LOG4NET-397:
Description:
Consider an application that uses two third-party assemblies:
- AssemblyA from Supplier A, compiled
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789012#comment-13789012
]
Dominik Psenner commented on LOG4NET-397:
-
Since you have to share assemblies, it
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789036#comment-13789036
]
Dominik Psenner commented on LOG4NET-395:
-
FWIW, you can contact the owner by
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789039#comment-13789039
]
Joe commented on LOG4NET-397:
-
... it may be time to learn about the GAC
1. I know about
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789054#comment-13789054
]
Dominik Psenner edited comment on LOG4NET-397 at 10/8/13 8:57 AM:
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner resolved LOG4NET-397.
-
Resolution: Invalid
Deployment issues have to be addressed by whoever's using log4net.
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789058#comment-13789058
]
Stefan Bodewig commented on LOG4NET-397:
Joe, you are right. When we considered
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789062#comment-13789062
]
Stefan Bodewig commented on LOG4NET-397:
type forwarding wouldn't work for 1.x -
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789065#comment-13789065
]
Joe commented on LOG4NET-397:
-
... if a third party library uses log4net and another third
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789073#comment-13789073
]
Joe commented on LOG4NET-397:
-
Using a privatePath attribute on a probing element in your
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789079#comment-13789079
]
Stefan Bodewig commented on LOG4NET-397:
So far I had assumed you had no
Hi all,
not sure whether I find an audience big enough or whether we need to
expand this to the user list.
One option to get out of the oldkey/newkey problems mentioned in
https://issues.apache.org/jira/browse/LOG4NET-397 would be to make the
move to a log4net2 assembly.
The short term plan
[
https://issues.apache.org/jira/browse/LOG4NET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789105#comment-13789105
]
Joe commented on LOG4NET-397:
-
So far I had assumed you had no influence on the suppliers
1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
not mind breaking backwards compatibility within 1.X even further. The next
good milestone could be 1.3 RC1 since we won't be compatible with log4j2 and
we should go to 2.X only if we port log4j2 features into log4net.
On 2013-10-08, Dominik Psenner wrote:
1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
not mind breaking backwards compatibility within 1.X even further. The next
good milestone could be 1.3 RC1 since we won't be compatible with log4j2 and
we should go to 2.X only if
1.2.11 already contained breaking changes and so did 1.2.12. Thus I would
not mind breaking backwards compatibility within 1.X even further. The
next
good milestone could be 1.3 RC1 since we won't be compatible with log4j2
and
we should go to 2.X only if we port log4j2 features into log4net.
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789220#comment-13789220
]
Mark Ward commented on LOG4NET-395:
---
The owner of the nuget package has made a post he
On 2013-10-04, Stefan Bodewig wrote:
I've contacted cincura.net via the NuGet website and hope to hear
back. It would be great to have her/him on board addressing the
packaging related issues and maybe help streamline the process of
publishing future packages.
Never heard back, but with
Never heard back, but with
http://blog.cincura.net/233419-log4net-nuget-package-updated-without-
some-goodies/
and https://github.com/cincuranet/log4net-nuget we could simply point
people to github and close all Nuget related issues immediately.
+1
Given the noise, an entry in the FAQ could be
On 2013-10-08, Dominik Psenner wrote:
Never heard back, but with
http://blog.cincura.net/233419-log4net-nuget-package-updated-without-
some-goodies/
and https://github.com/cincuranet/log4net-nuget we could simply point
people to github and close all Nuget related issues immediately.
+1
[
https://issues.apache.org/jira/browse/LOG4NET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789236#comment-13789236
]
Stefan Bodewig commented on LOG4NET-358:
see also
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-392:
---
Labels: nuget patch (was: patch)
Updating causing Config issue
Given the noise, an entry in the FAQ could be wise.
Probably - and maybe a pointer from the download page.
I'll take care of it tomorrow unless you beat me to it.
Please, take your time. :-)
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Psenner closed LOG4NET-395.
---
Resolution: Invalid
This is invalid as we don't control the nuget package.
See also
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789256#comment-13789256
]
Mark Strandness commented on LOG4NET-392:
-
That's fine... PLEASE REMOVE the
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789265#comment-13789265
]
Dominik Psenner commented on LOG4NET-392:
-
Hey Mark
I can feel your frustration,
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789265#comment-13789265
]
Dominik Psenner edited comment on LOG4NET-392 at 10/8/13 3:04 PM:
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-392:
---
Component/s: (was: Builds)
Updating causing Config issue
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-392.
Resolution: Won't Fix
we'd like to see this fixed but can't fix it as the Nuget package
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-392:
sorry, I can't seem to change the resolution without re-opening the issue.
Mark, you are
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig resolved LOG4NET-395.
Resolution: Won't Fix
invalid is not a proper resolution for an existing bug we just
[
https://issues.apache.org/jira/browse/LOG4NET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-358:
Visual Studio snippet within the deployment with NuGet
[
https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened LOG4NET-395:
Nuget packaging problem - Creates app.config file in ALL projects when
applying package.
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789281#comment-13789281
]
Mark Strandness commented on LOG4NET-392:
-
And now who in the hell are you? OK...
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789289#comment-13789289
]
Mark Strandness commented on LOG4NET-392:
-
Fine... you doing it for FREE.. I
[
https://issues.apache.org/jira/browse/LOG4NET-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Strandness closed LOG4NET-392.
---
This is a FINE company to get your software from and point their finger to
someone else...
If log4net2.x will imply a port of log4j2 then I think we should do log4net
1.3 and remove the .NET 1.x support.
On Tue, Oct 8, 2013 at 4:13 PM, Dominik Psenner dpsen...@gmail.com wrote:
1.2.11 already contained breaking changes and so did 1.2.12. Thus I
would
not mind breaking backwards
39 matches
Mail list logo