logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Ward (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-395) Nuget packaging problem - Creates app.config file in ALL projects when applying package.
Date Thu, 03 Oct 2013 16:26:42 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785317#comment-13785317
] 

Mark Ward commented on LOG4NET-395:
-----------------------------------

The nuget package link is http://www.nuget.org/packages/log4net/

It is not obvious that ASF does not maintain this package.  In the NuGet package manager in
Visual Studio it lists Created By as "Apache Software Foundation" but the owner is "cincura.net"

I don't think this issue is a duplicate although might be related because both focus on app.config.
 The nuget package is adding a new app.config file to the projects.  It even adds app.config
files to assembly projects.  If the project already contains an app.config file the nuget
package will add a console appender to the app.config.

It is also adding a new AssemblyInfo.log4net.cs file with the contents of "[assembly: log4net.Config.XmlConfigurator(Watch
= true)]" which breaks the build if the project already contains a xmlconfiguration declaration.


> Nuget packaging problem - Creates app.config file in ALL projects when applying package.
> ----------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-395
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-395
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 1.2.9, 1.2.10, 1.2.12
>            Reporter: Adam Lith
>
> When installing (or updating!) the log4net nuget package it either:
> * Adds an app.config file if none exists
> * Transforms the app.config file if one exists.
> And it does this to all the projects that you apply the package to (as always with nuget).
> This is incredibly annoying because then I have to manually delete the config files or
revert the transformations.
> The common practice for nuget-packaging is to not perform zero transforms or content-type
additions and instead supply a link in the description of the package to a tutorial for those
that don's know how to get started.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message