[
https://issues.apache.org/jira/browse/LOG4NET-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Mitchell updated LOG4NET-10:
---------------------------------
Attachment: asm-ver-desc-patterns.patch
Note: the patch was produced against revision 489241
Here is potential solution for adding the assembly version to the output. I
also included the assembly description attribute, as in our build process we
stamp every assembly with the svn revision as part of its version field, and
the svn url for its description field. Other assembly patterns useful to
people could easily be added.
%asm-ver is the pattern for version
%asm-desc is the pattern for description
The only reason I didn't use %v for the version attribute is because I also
added the description attribute.
> Add %v pattern to output assembly version
> -----------------------------------------
>
> Key: LOG4NET-10
> URL: https://issues.apache.org/jira/browse/LOG4NET-10
> Project: Log4net
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.2.9
> Environment: From sourceforege - 775175 - Daniel Cazzulino (kzu) -
> dcazzulino
> Reporter: Nicko Cadell
> Priority: Minor
> Attachments: asm-ver-desc-patterns.patch
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
