Hide Forgot
Description of problem: Migrating JCR package name in camel-case (e.g. 'globalArea' or 'defaultPackage') results in multiple directories with different names, some of them in camel case (globalArea) and some of the in lowercase completely (globalarea). See the following directory structure. defaultPackage |-- pom.xml |-- project.imports `-- src |-- main | |-- java | | `-- defaultpackage | | `-- defaultpackage | `-- resources | |-- defaultpackage | | `-- defaultpackage | |-- defaultPackage | | `-- Some\ custom\ file.txt | `-- META-INF | `-- kmodule.xml `-- test |-- java | `-- defaultpackage | `-- defaultpackage `-- resources `-- defaultpackage `-- defaultpackage Version-Release number of selected component (if applicable): 6.0.0-ER5 (also community 6.0.0-SNAPSHOT) Expected results: Either 'globalArea' or 'globalarea' should be used in all places. I am not sure which one is better is this case.
To be consistent with the current package name management, all the package name migrated are converted to lowercase before creation. Commit: 6.0.x https://github.com/droolsjbpm/drools-wb/commit/6a6abab9dedc23560036885eb79335816d279589
Verified fixed in 6.0.0-ER7.