Skip to content

Conversation

@robert-s-ubi
Copy link
Contributor

The "ocpp-v2_0" subproject was the first attempt at OCPP 2.0.1 support, which only allowed using this protocol version. It has been replaced by the new "ocpp-v2" implementation, which allows offering multiple OCPP versions in the Websocket handshake (currently OCPP 1.6 and OCPP 2.0.1) and is extensible for future OCPP 2.x versions.

Remove the deprecated "ocpp-v2_0" subproject to avoid confusion.

The "ocpp-v2_0" subproject was the first attempt at OCPP 2.0.1 support,
which only allowed using this protocol version. It has been replaced by
the new "ocpp-v2" implementation, which allows offering multiple OCPP
versions in the Websocket handshake (currently OCPP 1.6 and OCPP 2.0.1)
and is extensible for future OCPP 2.x versions.

Remove the deprecated "ocpp-v2_0" subproject to avoid confusion.
@robert-s-ubi robert-s-ubi force-pushed the remove_obsolete_ocpp-v2_0_tree branch from 197db60 to b1f5b4a Compare December 5, 2025 16:06
@robert-s-ubi robert-s-ubi merged commit e1d4a19 into master Dec 5, 2025
4 checks passed
@robert-s-ubi robert-s-ubi deleted the remove_obsolete_ocpp-v2_0_tree branch December 5, 2025 16:09
robert-s-ubi added a commit that referenced this pull request Dec 5, 2025
The last rebase of PR #371 left files that were supposed to be deleted,
because they had been altered since the PR had been created.

Remove the leftover files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants