Skip to content

Conversation

@robert-s-ubi
Copy link
Contributor

Clean up the project structure, separating OCPP 1.6J and OCPP 1.6S support.

Rename the artifacts to more descriptive names.

Unify names and descriptions across all gradle and maven build files.

Update README.md with a description of the new project structure.

Bump the library version to 2.0 and the artifacts versions to 2.0.0.

Also clean up dependencies and make them consistent, and unify spacing
across pom.xml files.
@robert-s-ubi robert-s-ubi force-pushed the clean_up_project_structure branch from 436f404 to 2711952 Compare December 8, 2025 15:23
Copy link
Contributor

@jmluy jmluy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor comment/question but otherwise LGTM

<version>0.0.1-SNAPSHOT</version>
<name>json-server-implementation </name>
<description>Example Spring Application of a json server </description>
<artifactId>ocpp16-json-server-example</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a bug but do you want to rename the directory for the server example to match the client?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really. I renamed the OCPP-J directory, because it was sticking out like a sore thumb, but otherwise left existing directory names untouched.

The inconsistencies in the directory names here are minor, so I think renaming them is not worth the possible confusion.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, it's just a minor inconsistency.

@robert-s-ubi robert-s-ubi merged commit d62ae22 into master Dec 12, 2025
4 checks passed
@robert-s-ubi robert-s-ubi deleted the clean_up_project_structure branch December 12, 2025 07:36
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.

3 participants