Skip to content

resolve "Migrate ShipNodeConfiguration to builder pattern"#5

Open
wursthos wants to merge 2 commits into
developfrom
3-migrate-shipnodeconfiguration-to-builder-pattern
Open

resolve "Migrate ShipNodeConfiguration to builder pattern"#5
wursthos wants to merge 2 commits into
developfrom
3-migrate-shipnodeconfiguration-to-builder-pattern

Conversation

@wursthos
Copy link
Copy Markdown
Collaborator

@wursthos wursthos commented Apr 28, 2026

closes #3
closes #11

start overhauling ShipNodeConfiguration;

slightly improve ServiceRegistry;

add ShipConfig with fluent builder;

make ShipClientHandler#close null-safe;

hopefully finish ShipConfig;
begin integrating new config;

extract ConfigBuilder;
streamline ServiceRegistry;

further streamline ServiceRegistry;
fix default mDNS domain;

remove ship-cli subproject;
update demo subproject;
update CHANGELOG;
improve and test ServiceRegistry;

rename all CallBacks to Listeners;
@wursthos wursthos added this to jEEBus Apr 28, 2026
@wursthos wursthos added the configuration Improvements or additions to configuration label Apr 28, 2026
@wursthos wursthos linked an issue Apr 28, 2026 that may be closed by this pull request
@github-project-automation github-project-automation Bot moved this to Backlog in jEEBus Apr 28, 2026
@wursthos wursthos removed this from jEEBus Apr 30, 2026
Comment thread projects/ship/src/main/java/org/openmuc/jeebus/ship/api/ConfigBuilder.java Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

configuration Improvements or additions to configuration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make Brand, Type and Model in TXT Record customizable Migrate ShipNodeConfiguration to builder pattern

2 participants