[
https://issues.apache.org/jira/browse/JCR-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090130#comment-13090130
]
Alex Parvulescu commented on JCR-3058:
--------------------------------------
Good idea.
Is it possible to have the analyzer point to the problems? Rather than relying
on manual validation of the properties found in the broken bundle?
Maybe a status message after the dump? along the lines of:
- bundle check ok
or
- bundle check failed: broken properties are (or might be): p1, p2...
For example, I'm looking at a bundle that has >35 properties, how can I know
what is going on?
> BundleDumper to analyze broken bundles
> --------------------------------------
>
> Key: JCR-3058
> URL: https://issues.apache.org/jira/browse/JCR-3058
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 2.3.0
>
>
> The BundleReader fails if it can't read a bundle. We should have a tool to
> analyze broken bundles.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
