Bug 977885 - Make the jcr2vfs migration tool more user friendly
Summary: Make the jcr2vfs migration tool more user friendly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Jervis Liu
QA Contact: Petr Široký
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-25 14:19 UTC by Petr Široký
Modified: 2014-02-21 13:29 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-27 09:25:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Široký 2013-06-25 14:19:35 UTC
Note: This is more like enhacement than bug.

Description of problem:
The jcr2vfs migration tool should be IMHO more user friendly. Following things could help with that:

(1) The "runMigration.sh" should accept "-h" parameter that would briefly explain what the tool is intented for, what are the inputs (parameters) and what are the outputs - just basic help.

(2) I am not sure about the default behavior - e.g. expecting the input somewhere and if its not there throw an exception. What about if no parameters are set, just print the help saying that the user needs to specify input jcr repo and output vfs repo (dir)? e.g. the default behavior (if no parameters specified) would be so print the help.

(3) I would suggest to not print exception stacktraces to stdout at all. I agree that the exception is useful for debugging, but it would be better I guess to print it into log file and just print meaningful error message to the stdout.

WDYT?

Version-Release number of selected component (if applicable):
6.0.0-DR5

Comment 2 Petr Široký 2013-06-27 09:25:33 UTC
Closing this issue and moving the discussion to community Jira as that is probably the best place to have the enhancements listed. https://issues.jboss.org/browse/GUVNOR-2020


Note You need to log in before you can comment on or make changes to this bug.