logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Lith (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (LOG4NET-395) Nuget packaging problem - Creates app.config file in ALL projects when applying package.
Date Fri, 04 Oct 2013 07:18:59 GMT

     [ https://issues.apache.org/jira/browse/LOG4NET-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adam Lith reopened LOG4NET-395:
-------------------------------


It is not a duplicate although related to 392.
What they have in common is that they both have something to do with the nuget packaging,
but What they highlight as an issue are different. (i.e. both issues have a need to be fixed
separately)

> 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