| 42 | | * |
| | 42 | * First I'll note which system propeties should be used for help cleaning the static paths from FEM: |
| | 43 | * sophie2.development - True if Sophie 2 is launched under Fake or True launchers in Eclipse |
| | 44 | * sophie2.testing - True if we are in testing phase. |
| | 45 | * sophie2.config.file - String with the config file location |
| | 46 | * java.class.path - the class path which is used under fake to gather the module names |
| | 47 | * user.dir - location of the current user directory |
| | 48 | * sophie2.module.paths - String with the location of all the modules to target/classes(or target/test-classes) folder. This is done because there is no other (known) way(under Fake launch) to extract the paths to the sophie modules. The java class path didn't do the work because there are some other packages and we use prefix to extract only org.sophie2 modules, but if the prefix become different a problem will occur. |
| | 49 | * Some of the logic how the things work should be changed: |
| | 50 | * fillFakeModulePaths should not fill the paths using the class path but the sophie2.module.paths system property. |
| | 51 | * in roRoots there is no need to append target/classes and target/test-classes suffixes to the paths because src/main(test)/resources locations won't be read only roots anymore. All resources should be searched in target folder where are the compiled classes. |
| | 52 | * rwRoot will |
