Castle & log4net 1.2.11

179 views
Skip to first unread message

Artur Dorochowicz

unread,
Aug 6, 2012, 3:40:33 PM8/6/12
to Castle Project Development List
Hi group,

For some reason I believed that Castle * 3.1 would link to log4net
1.2.11.
I was quite surprised to see that it wasn't.

As you probably know the change between log4net 1.2.10 and 1.2.11
cannot be done outside of
projects that use it due to the fact that nuget package for 1.2.11
uses binaries with different
strong name than 1.2.10.

Are there any plans for an update to log4net 1.2.11?

Best regards
Artur

Krzysztof Kozmic

unread,
Aug 6, 2012, 4:16:02 PM8/6/12
to castle-pro...@googlegroups.com
not anytime soon

-- 
Krzysztof Kozmic

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.

Artur Dorochowicz

unread,
Aug 6, 2012, 4:31:49 PM8/6/12
to Castle Project Development List
Is there any particular reason for this or is that just lack of
resources?

Best regards
Artur

On Aug 6, 10:16 pm, Krzysztof Kozmic <krzysztof.koz...@gmail.com>
wrote:
> not anytime soon
>
> --
> Krzysztof Kozmic
>
>
>
>
>
>
>
> On Tuesday, 7 August 2012 at 5:40 AM, Artur Dorochowicz wrote:
> > Hi group,
>
> > For some reason I believed that Castle * 3.1 would link to log4net
> > 1.2.11.
> > I was quite surprised to see that it wasn't.
>
> > As you probably know the change between log4net 1.2.10 and 1.2.11
> > cannot be done outside of
> > projects that use it due to the fact that nuget package for 1.2.11
> > uses binaries with different
> > strong name than 1.2.10.
>
> > Are there any plans for an update to log4net 1.2.11?
>
> > Best regards
> > Artur
>
> > --
> > You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
> > To post to this group, send email to castle-pro...@googlegroups.com (mailto:castle-pro...@googlegroups.com).
> > To unsubscribe from this group, send email to castle-project-d...@googlegroups.com (mailto:castle-project-d...@googlegroups.com).

Krzysztof Kozmic

unread,
Aug 6, 2012, 4:40:36 PM8/6/12
to castle-pro...@googlegroups.com
it is a major breaking change and major PITA

-- 
Krzysztof Kozmic

To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.

hammett

unread,
Aug 6, 2012, 4:49:22 PM8/6/12
to castle-pro...@googlegroups.com
You can do a binding redirect, right?
> To post to this group, send email to castle-pro...@googlegroups.com.
> To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
>



--
Cheers,
hammett
http://hammett.castleproject.org/

Krzysztof Kozmic

unread,
Aug 6, 2012, 4:50:15 PM8/6/12
to castle-pro...@googlegroups.com
No, you can't. The key is different. Redirect works if the only thing changed is version number


-- 
Krzysztof Kozmic

Artur Dorochowicz

unread,
Aug 6, 2012, 5:10:40 PM8/6/12
to Castle Project Development List
PITA - yeah, tell me about it.

Problem is that more and more libraries start depending on log4net
1.2.11
(and yes, I know that they quite often do it without much thinking,
but that is a fact) and when you depend on Castle you cannot use those
updates.

Maybe a parallel release is something that could be accomplished,
so a version against log4net 1.2.10 and another one against 1.2.11.
This is an approach that e.g. Common.Logging uses.

Best regards and thanks for your efforts in developing Castle.
Artur

On Aug 6, 10:40 pm, Krzysztof Kozmic <krzysztof.koz...@gmail.com>
wrote:
> it is a major breaking change and major PITA
>
> --
> Krzysztof Kozmic
>
>
>
>
>
>
>
> On Tuesday, 7 August 2012 at 6:31 AM, Artur Dorochowicz wrote:
> > Is there any particular reason for this or is that just lack of
> > resources?
>
> > Best regards
> > Artur
>
> > On Aug 6, 10:16 pm, Krzysztof Kozmic <krzysztof.koz...@gmail.com (http://gmail.com)>

Krzysztof Kozmic

unread,
Aug 6, 2012, 5:28:40 PM8/6/12
to castle-pro...@googlegroups.com
Yeah, either way you're going to upset people. This is madness, and I'm not giving into it.

That being said, feel free to provide an unofficial package for v1.2.11.

-- 
Krzysztof Kozmic

To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.

Anthony Abate

unread,
Dec 19, 2013, 1:35:35 PM12/19/13
to castle-pro...@googlegroups.com
Couldn't this be fixed by creating multiple Castle.Services.Logging.Log4netIntegration libraries?   I know it seems silly.. but kinda seems like the correct thing to do at this point...  You have to treat a key change like that as if it is different library all together...  

In my opinion, Log4net lost a lot of credibility when they changed their key.. but regardless... they are on version 1.2.13 and they are still producing 2 binaries with each build...   

That being said.. the newest build with the old key doesnt work anymore... they have made a change to their api so it seems that castle is pegged at version 1.2.10... 




On Friday, January 4, 2013 6:06:36 PM UTC-5, Chris Constantin wrote:
Couldn't find such an unofficial package, so I just published one:

Cheers,
Chris
Reply all
Reply to author
Forward
0 new messages