You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Curt Arnold (JIRA)" <ji...@apache.org> on 2011/08/25 04:38:28 UTC
[jira] [Created] (LOG4NET-308) Incorporate a compatibility checker
to the build
Incorporate a compatibility checker to the build
------------------------------------------------
Key: LOG4NET-308
URL: https://issues.apache.org/jira/browse/LOG4NET-308
Project: Log4net
Issue Type: Task
Reporter: Curt Arnold
The log4j build uses CLIRR to check that there have been no changes that break compatibility with previous releases. I would assume that there would have to be a similar tool in the .NET space and it would be beneficial to have any automated check instead of trying to find any changes via code review.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (LOG4NET-308) Incorporate a compatibility
checker to the build
Posted by "Stefan Bodewig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4NET-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098678#comment-13098678 ]
Stefan Bodewig commented on LOG4NET-308:
----------------------------------------
I asked for recommendations on the lucene.net list, http://bitwidgets.com/default.html - which is free for OSS - was brought up and looks interesting. Will wait for more results, though.
Apart from checking version compatibilitywe could also use a Clirr-like tool to compare the DLLs targeting the different platforms - i.e. check whether the many compilation symbols introduce unexpected API differences.
> Incorporate a compatibility checker to the build
> ------------------------------------------------
>
> Key: LOG4NET-308
> URL: https://issues.apache.org/jira/browse/LOG4NET-308
> Project: Log4net
> Issue Type: Task
> Reporter: Curt Arnold
> Fix For: 1.2 Maintenance Release
>
>
> The log4j build uses CLIRR to check that there have been no changes that break compatibility with previous releases. I would assume that there would have to be a similar tool in the .NET space and it would be beneficial to have any automated check instead of trying to find any changes via code review.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (LOG4NET-308) Incorporate a compatibility checker
to the build
Posted by "Stefan Bodewig (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4NET-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bodewig updated LOG4NET-308:
-----------------------------------
Fix Version/s: 1.2 Maintenance Release
I agree this would be a good idea but don't know of anything similar to clirr for .NET assemblies.
> Incorporate a compatibility checker to the build
> ------------------------------------------------
>
> Key: LOG4NET-308
> URL: https://issues.apache.org/jira/browse/LOG4NET-308
> Project: Log4net
> Issue Type: Task
> Reporter: Curt Arnold
> Fix For: 1.2 Maintenance Release
>
>
> The log4j build uses CLIRR to check that there have been no changes that break compatibility with previous releases. I would assume that there would have to be a similar tool in the .NET space and it would be beneficial to have any automated check instead of trying to find any changes via code review.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira