Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions doc/changes/changes.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
# Changes

* [4.2.3](changes_4.2.3.md)
* [4.2.2](changes_4.2.2.md)
* [4.2.1](changes_4.2.1.md)
* [4.2.0](changes_4.2.0.md)
Expand Down
11 changes: 11 additions & 0 deletions doc/changes/changes_4.2.3.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# OpenFastTrace 4.2.3, released 2026-03-01

Code name: Protobuf file support

## Summary

In this release we added support for Protobuf definition files.

## Bugfixes

* #490: Add tag importer support for Protobuf (`.proto`) files
5 changes: 3 additions & 2 deletions doc/user_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,13 +32,13 @@ The document is also helpful for people who just want to get an insight on what
* IT Support personnel
* People responsible for picking tools (who we recommend should be users too)

Of course requirement engineering and tracing are useful outside the software domains too.
Of course, requirement engineering and tracing are useful outside the software domains too.

### What is Requirement Tracing?

OpenFastTrace is a requirement tracing suite. Requirement tracing helps you to keep track of whether you actually implemented everything you planned to in your specifications. It also identifies obsolete parts of your product and helps you to get rid of them.

The foundation of all requirement tracing are links between documents, implementation, test, reports and whatever other artifacts your product consists of.
The foundation of all requirement tracing is links between documents, implementation, test, reports and whatever other artifacts your product consists of.

Let's assume you compiled a list of five main features your users asked for. They are very coarse but provide a nice overview of what your project is expected to achieve. Next you decide to write a few dozen user stories to flesh out the details of what your users want.

Expand Down Expand Up @@ -772,6 +772,7 @@ recognized file types:
**Configuration and Serialization Formats**

* JSON (`.json`)
* Protobuf (`.proto`)
* TOML (`.toml`)

**Markup languages**
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ public class TagImporterFactory extends ImporterFactory
"m", "mm", // Objective C
"php", // PHP
"pl", "pm", // Perl
"proto", // Protobuf
"py", // Python
"robot", // Robot Framework
"pu", "puml", "plantuml", // PlantUML
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ protected List<String> getSupportedFilenames()
"foo.bat", "foo.java", "foo.c", "foo.C", "foo.c++", "foo.c#", "foo.cc", "foo.cfg",
"foo.conf", "foo.cpp", "foo.cs", "foo.feature", "foo.groovy", "foo.h", "foo.H", "foo.hh", "foo.h++",
"foo.htm", "foo.html", "foo.ini", "foo.js", "foo.mjs", "foo.cjs", "foo.ejs", "foo.ts", "foo.json",
"foo.lua", "foo.m", "foo.mm", "foo.php", "foo.pl", "foo.pls", "foo.pm", "foo.py", "foo.sql", "foo.r",
"foo.lua", "foo.m", "foo.mm", "foo.php", "foo.pl", "foo.pls", "foo.pm", "foo.proto", "foo.py", "foo.sql", "foo.r",
"foo.rs", "foo.sh", "foo.sv", "foo.v", "foo.inc", "foo.yaml", "foo.yml", "foo.xhtml", "foo.zsh",
"foo.clj", "foo.kt", "foo.scala",
"foo.pu", "foo.puml", "foo.plantuml", "foo.go", "foo.robot", "foo.tf", "foo.tfvars", "foo.toml");
Expand Down
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@
<build>
<plugins>
<plugin>
<!-- Deployment of this module not required -->
<!-- Deployment of this module is not required -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>3.1.4</version>
Expand Down
Loading