N release, milestone 2 (NM2 1.1.1943)

Unified logging for individual data accesses, artifact types, and link types

YT now reports adapter-specific information on a more detailed level, according to the individual definitions in the current YT configuration. It also reports some additional information on YT start and on extraction of traceability data into CSV files (in batch mode). Furthermore, the log messages are now reported by specific loggers depending on which area they belong to.

In more detail, the following information is logged now:

Logger com.yakindu.traceability.formalized.setup

  • On YT start or reload: YT lists all Eclipse projects in the workspace in the form "YT found project name" or „YT found no projects”, respectively.

Logger com.yakindu.traceability.formalized.dataaccess

  • For each data access:
    • When a new resource (e.g. a file) is found: "DataAccess name found resource resource-name"
    • If the data access defines a file pattern and no file is found for that pattern when YT loads: "DataAccess name found no file for pattern pattern"
    • When a file has been changed and re-read: "File path has been updated"

Logger com.yakindu.traceability.formalized.artifacttype

  • For each artifact type, whenever the artifacts of that type have been loaded or updated:

Updated artifact type name
Counts:
No of changed artifacts: number
(further adapter-specific lines in the form " caption: number")
Times:
(adapter-specific lines in the form " caption: measurement ms")

Logger com.yakindu.traceability.formalized.linktype

  • For each link type, whenever the links of that type have been loaded or updated:

Updated links of type name
Counts:
No of links: number
(further adapter-specific lines in the form " caption: number")
Times:
(adapter-specific lines in the form " caption: measurement ms")

Logger com.yakindu.traceability.formalized.dataextract

  • Whenever traceability data is exported into CSV files:
    • For linked artifacts: " number linked artifacts exported in measurement ms."
    • For linkable artifacts: " number linkable artifacts of type exported in measurement ms."
    • For links: " number links of type exported in measurement ms."

Logger com.yakindu.traceability.formalized.queryextract

  • Whenever query results are exported into CSV files: " number result rows of query name exported in measurement ms."

Note that there are currently some limitations:

  • The number of linked artifacts is currently not yet exported separately for each type.
  • PTC and Native File adapters do not yet report link-related information.

Bug Fixes

The text editor adapter saved modified files when creating links by drag-and-drop

When you modified a text file that contains artifacts, it needs to be saved before creating text editor links. In certain rare situations, YT auto-saved text files when creating a link by drag-and-drop. This was not intended, because it might save changes that you didn’t actually intend to keep. YT now enforces manual saving of modified files also in this situation.

The query function „tracesFromTo” did not work for cycles

Execution of queries with the query function „tracesFromTo” could lead to errors when the traceability model contained cycles. This should work now.