#8 Inconsistent use of folders in parameters

[Anonymous]

Hi,

Just a small thing but I have noticed that command line parameters are not consistent in how they treat subfolders in provided path.
For example, my project folder structure is:
d:\Projects\SQL\Tests\Sanity Tests
with two subfolders:
> "Environments"
> "Definitions"

When providing those folders as parameters for DB Sanity I get what follows:
1. dbsanity -i \Definitions \Environments\restore_test
DB Sanity result:
Local classpath: .;c:\Program Files\dbsanity\dbsanity-0.9.3\bin;c:\Program Files\dbsanity\dbsanity-0.9.3\lib\*
Exception in thread "main" org.databene.commons.ConfigurationError: Test definition folder not found: d:\Definitions
at org.databene.dbsanity.DbSanity.checkPreconditions(DbSanity.java:500)
at org.databene.dbsanity.DbSanity.execute(DbSanity.java:290)
at org.databene.dbsanity.Main.main(Main.java:50)

This would be ok. There's no d:\Definitions folder.

2. dbsanity -i Definitions \Environments\restore_test
Result: Works. Import of tables started.

3. dbsanity -i Definitions Environments\restore_test
Result: Works as well. Import of tables started.

Conclusion:
When path to Definitions is provided as "\Definitions" DB Sanity acts correctly by interpreting \ as root on the drive. However, it does not work the same for Environments folder.

Expected:
DB Sanity should return an error that folder "Environments" could not be found or similar when running application with \Environments\restore_test argument.