You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/02/18 20:46:38 UTC
[jira] Commented: (INFRA-3461) Some subversion commits are not
showing in Jira with subversion plugin after upgrade of Jira
[ https://issues.apache.org/jira/browse/INFRA-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996577#comment-12996577 ]
Kathey Marsden commented on INFRA-3461:
---------------------------------------
Thank you so very much Ulrich for the fix!
I will be out next week but let the Derby community know to reopen this issue if they see any problems. I have not come across any this morning. I am curious to know the fixes and it would be nice to have them here in the Jira so they can be used for reference on the next Jira upgrade.
> Some subversion commits are not showing in Jira with subversion plugin after upgrade of Jira
> --------------------------------------------------------------------------------------------
>
> Key: INFRA-3461
> URL: https://issues.apache.org/jira/browse/INFRA-3461
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Kathey Marsden
> Assignee: Ulrich Stärk
>
> At the Derby project starting Feb 16, 2011, the community started noticing some issues were not showing subversion commits tab in JIRA. Some were fixed by Uli on the #asfinfra channel, like DERBY-4913 which was due to a regular expression issue with the plugin setup. In general Uli thinks that the problems are related to tuning the settings on the plugin.
> Some issues like
> https://issues.apache.org/jira/browse/DERBY-4282
> which should have commit:
> r803336 | bpendleton | 2009-08-11 17:48:11 -0700 (Tue, 11 Aug 2009) | 23 lines
> and
> https://issues.apache.org/jira/browse/DERBY-4837
> r1069910 | kristwaa | 2011-02-11 10:10:59 -0800 (Fri, 11 Feb 2011) | 7 lines
> are still problematic.
> I am not entirely sure but I think maybe that some issues that worked even after the upgrade are not working now, but I don't have any concrete examples so that may not be the case.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira