db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5899) Modify the SubversionLogVTI demo to have a jira_issue column
Date Fri, 10 Aug 2012 00:32:18 GMT
Kathey Marsden created DERBY-5899:

             Summary: Modify the SubversionLogVTI demo  to have a jira_issue column
                 Key: DERBY-5899
                 URL: https://issues.apache.org/jira/browse/DERBY-5899
             Project: Derby
          Issue Type: Improvement
          Components: Demos/Scripts
    Affects Versions:
            Reporter: Kathey Marsden

As it looks as though the subversion plugin won't be back anytime soon. It would be nice to
modify the SubversionLogVTI demo  to have another column for jira_issue  which would be null
if there is nothing matching the jira issue pattern in the description.  

This would make it easier  to load up the log in a derby db for queries to use as a alternative
to the plugin in the short term.

It would be good to somehow indicate a branch as well, but not sure how that would work in
a generic way for the demo..  Maybe a second VTI could load up the detail that prints with
svn log -v to another table or handle it outside of the demo VTI all together by just generating
different svn log output files for each branch and specify the branch with the load.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message