[ http://issues.apache.org/jira/browse/LOG4NET-10?page=all ]
Nicko Cadell updated LOG4NET-10:
--------------------------------
Description:
n an environment where multiple versions of the same
assembly is being used simultaneously by different
applications, it's very useful to get the version of
the assembly that is emiting the logging event.
I'll add this right away. If you want the (rather
trivial) code, I can post it.
Daniel Cazzulino
---
Well, the code is not trivial (to implement in a performant
way), and our project is a little time-constrained.
If I can, I'll try to make it, most probably in the
LogManager.GetLogger method (the usage pattern indicates
this will probably be a single static call per-class using
logging)... I don't know.
Daniel Cazzulino
was:
n an environment where multiple versions of the same
assembly is being used simultaneously by different
applications, it's very useful to get the version of
the assembly that is emiting the logging event.
I'll add this right away. If you want the (rather
trivial) code, I can post it.
Daniel Cazzulino
---
Well, the code is not trivial (to implement in a performant
way), and our project is a little time-constrained.
If I can, I'll try to make it, most probably in the
LogManager.GetLogger method (the usage pattern indicates
this will probably be a single static call per-class using
logging)... I don't know.
Daniel Cazzulino
Priority: Minor (was: Major)
There seems to be low demand for this feature. Changing the priority to Minor.
> Add %v pattern to output assembly version
> -----------------------------------------
>
> Key: LOG4NET-10
> URL: http://issues.apache.org/jira/browse/LOG4NET-10
> Project: Log4net
> Type: New Feature
> Components: Core
> Versions: 1.2.9
> Environment: From sourceforege - 775175 - Daniel Cazzulino (kzu) - dcazzulino
> Reporter: Nicko Cadell
> Priority: Minor
>
> n an environment where multiple versions of the same
> assembly is being used simultaneously by different
> applications, it's very useful to get the version of
> the assembly that is emiting the logging event.
> I'll add this right away. If you want the (rather
> trivial) code, I can post it.
> Daniel Cazzulino
> ---
> Well, the code is not trivial (to implement in a performant
> way), and our project is a little time-constrained.
> If I can, I'll try to make it, most probably in the
> LogManager.GetLogger method (the usage pattern indicates
> this will probably be a single static call per-class using
> logging)... I don't know.
> Daniel Cazzulino
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
