Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.10.1.1
-
None
-
None
-
Newcomer
Description
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.
Attachments
Issue Links
- is related to
-
DERBY-6256 Move the XmlVTI into the product.
- Closed