Use versioning properly #104
Description
This issue can be closed as soon as people in charge have taken note and have discussed it. As a 10+ year Java developer I honestly find dealing with PSF frustrating because it does not use Maven versions as they are intended to be used. The latest iteration is still on version 1.0.0 even though it has seen major changes.
For a tool like DTLS-Fuzzer, versioning matters little since it is not a library, and other tools are unlikely to build on it. For a library like PSF versioning matters a lot, since many tools, including DTLS-Fuzzer build on it. Even if not published to the global maven repository, use of versioning still matters. To give an example, because everything is version 1.0.0, this prevents me from having two "versions" of PSF (e.g., one before the RA extension, and one after) in my local repository. This in turn creates various issues when building/switching between tools which use different "versions". There are various situations when I would want need to deploy multiple "versions" of PSF (debugging, etc).
Please, for future major changes (e.g., that break the API), update also the version. I don't mind how you update it, as long as it is different from older versions. Tools ported to the latest will of course also need to have their POM updated to use the latest version of PSF. This is completely standard practice.