Description of problem:
When trying to migrate the JCR repository that has the data stored in real database (e.g. mysql or postgresql) the migration tool throws following exception:
Exception in thread "main" java.lang.IllegalStateException: The unnestedVersionDir (/home/psiroky/work/jcr2vfs/guvnor-5.3-with-mysql/brms-standalone-5.3.1/jboss-as/bin/version) and the nestedVersionDir (/home/psiroky/work/jcr2vfs/guvnor-5.3-with-mysql/brms-standalone-5.3.1/jboss-as/bin/repository/version) does not exist.
	at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrater.determineJcrRepositoryRootDirectory(Jcr2VfsMigrater.java:154)
	at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrater.setupDirectories(Jcr2VfsMigrater.java:92)
	at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrater.migrateAll(Jcr2VfsMigrater.java:70)
	at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrater$Proxy$_$$_WeldClientProxy.migrateAll(Jcr2VfsMigrater$Proxy$_$$_WeldClientProxy.java)
	at org.drools.workbench.jcr2vfsmigration.Jcr2VfsMigrationApp.main(Jcr2VfsMigrationApp.java:36)


Problem is that the migration tool expects "version" directory inside the repository directory which is only true when the JCR repo is using embedded db. When real db is used the "version" dir is not created and the directory structure is:

repository/index/...
workspaces/default/...
repository.xml

Workaround is to create empty dir "repository/version", then the migration is successful.


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

How reproducible:


Steps to Reproduce:
1. Download the attached repo and unzip it.
2. Use the directory with the zip content as "-i" parameter for migrator.


Actual results:
Exception is thrown.


Expected results:
Migration is successfully completed.