Filters listed are dependencies in pom.xml of Tikal are not completed to run the command
Issue #699
new
Dependencies listed in okapi/tikal/pom.xml is not complete to run tikal from Eclips using some filters. For example, okapi-filter-markdown is not listed. This is fine for compilation but the command silently fails to run when a Markdown file (.md suffix) is specified to be extracted. Because of the issue #698, tikal mysteriously fails, without telling the fact the markdown filter classes were not loaded.
All the filter packages whose filter classes are listed in okapi/core/src/main/resources/net/sf/okapi/common/filters/DefaultFilters.properties must be listed as run-time (or compile time?) dependencies so that the Tikal run from Eclipse debugger can find all the filters.
Comments (3)
-
-
I would lower the priority of this bug since:
- issue #698 was resolved and the logging is now visible in Eclipse
- it is possible / easier / recommended to debug a filter using test units in the filter itself
-
- marked as minor
- Log in to comment
How critical is it to be able to debug every filter from tikal under Eclipse?
Unless I needed to debug tikal itself I’ve never needed this.
Most of the time adding a test unit to the filter under debug is the best approach, tikal only gets in the way.
On the other side I totally love using tikal to quickly experiment with filters from command line, not in Eclipse.
I would hate making tikal depend on everything.
Not sure if really a bug. But even if we agree it is, I don’t think it is a Priority “major”