...
The key to troubleshooting the stack trace is knowing that the last element is the most inward exception (opposite from typical Java stacktraces). There is nothing wrong with your import.properties file, this is simply the first thing cernunnos does because import.crn starts with:
| Code Block |
|---|
<properties location="classpath://properties/db/entities/import.properties"> |
Look at the bottom of the stacktrace, here is your real problem. If you look at the upper Caused by's you can figure out where Cernunnos was. In this case, it was in the import-layout_v2-6.crn file, with the node hierarchy: /with/subtasks/sql-transaction/xslt
...