Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
TeeTime
TeeTime
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 95
    • Issues 95
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • TeeTime
  • TeeTimeTeeTime
  • Issues
  • #298

Closed
Open
Opened Oct 03, 2016 by Nils Christian Ehmke@nieMaintainer

ClassNameRegistryCreationFilter should optionally throw exception

When the ClassNameRegistryCreationFilter currently cannot find the directory or the mapping file, it logs an error and then returns. However, this behaviour makes it difficult to find out whether the import of a monitoring log was successful or not. Instead, the filter (and consequently the Dir2RecordsFilter as well) should provide a property or a constructor flag to switch the behaviour to: throw an actual exception in case of an error. This would lead to an ExecutionException thrown by the Execution, which then could be handled by the application.

(Version is 2.1)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: teetime/teetime#298