Eclipse Java (JDT)

The Eclipse Java data access provides access to artifacts for the Java artifact provider in Java files.

The blog post "Tracing requirements and source code" gives a general overview of identifying source code elements as traceable artifacts and linking them to other artifact types, e.g., requirements.

Data access

Open the YT configuration with the YT configuration editor, and add a new data access as described in section "Data accesses". Select Eclipse Java as data access type.

Within the configuration panel, you can specify file patterns consisting of Eclipse projects, folders or filename patterns describing the Java files relevant for traceability.

Supported keyword:

  • resource – A pattern for a project, folder or file in the workspace.

The configuration may contain several resource definitions. In this case, YT takes the union of all patterns into account.

Independent of any resource definitions, YT takes only files with filename extension .java into account.

Please note that the resources have to reside in an Eclipse Java project.

Example:

In this example, YT evaluates all *.java files in project com.yakindu.yt.mt.java, folder name beginning with src.

Configuration

No configuration available yet.

Artifact type

The Java artifact type recognizes Java elements such as classes, methods and properties in a specified set of relevant files, but not individual statements within a method. The relevant files are specified in the Java data access. As a rule-of-thumb, YT recognizes all elements that appear in the outline view for Java-files.

Configuration

All configuration is done in the data access. An Eclipse Java artifact type does not support any further configuration.

Version

An artifact’s version is used for suspicious links validation. Artifacts of this type do not provide a version.