Skip to content

Dirigible 14.17.0: integration focus, full Java support, IDE as home - #317

Open
delchev wants to merge 1 commit into
mainfrom
sync-dirigible-14.17.0
Open

Dirigible 14.17.0: integration focus, full Java support, IDE as home#317
delchev wants to merge 1 commit into
mainfrom
sync-dirigible-14.17.0

Conversation

@delchev

@delchev delchev commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Iapetus is the integrations edition - Apache Camel is the focus, there is no BPM and no Intent Driven tooling - and its users should land in the Workbench, not on the platform's Home launchpad. This retargets to Dirigible 14.17.0 and makes all of that explicit.

Version

codbex-platform-parent 13.6.0 → 14.17.0 (parent releases track Dirigible releases 1:1). Supersedes #316 (dependabot → 14.11.0).

Full Java support

Added engine-java (in-process javac + the bean container), data-store-java (Java @Entity → Hibernate), the api-modules-java SDK, ide-java-lsp (JDT.LS), ide-java-debug (the DAP bridge) and the Java / Java Debug views.

One caveat worth knowing, documented in the pom: the client SDK exposes org.eclipse.dirigible.sdk.bpm, so api-modules-java → api-bpm → engine-bpm-flowable puts the Flowable engine on the classpath. I tried excluding api-bpm: it builds and the context boots, but it leaves sdk.bpm broken the moment client code touches it. Not worth the trap - so the engine stays and only the BPM tooling is left out (no BPMN editor, no Processes perspective, no BPM menus or templates; none of which this edition ever shipped). If you want Flowable genuinely out, the fix belongs upstream: decouple the Java SDK from api-bpm.

No Intent Driven tooling

There is no engine-intent here, so resources-builder (the conversational Builder shell, new in group-ui at 14.16.0) is excluded rather than shipped with nothing behind it. resources-inbox is excluded for the same reason - the BPM task inbox has no BPM surface in this edition.

Home is the Workbench

DIRIGIBLE_HOME_URL=services/web/shell-ide/, overriding the 14.16.0+ default of services/web/home/. The launchpad stays reachable at /services/web/home/; only the / redirect changes.

Consequence: upstream's HomepageRedirectIT asserts the platform default and therefore cannot pass here - it leaves the common suite. The edition's own HomePageIT (Workbench welcome view on /) guards the override and needed no change.

Camel

No dependency change was needed: template-camel at 14.17.0 is an aggregator that already depends on template-camel-cron-route and template-camel-http-route. I first added both explicitly, then verified on a running instance that they are offered without the explicit deps, and removed them again - the pom now just annotates the aggregator so nobody re-adds them.

UI overrides

components/ui/menu-help and view-welcome are forks of upstream files and had drifted: the help menu was still CommonJS without the conditional OpenAPI entry and kept its catalogs in translations/, where nothing reads them (only i18n/<locale>/ is scanned - the Bulgarian catalog was dead); view-welcome had a misspelled require form-item flag, the retired --fdAvatar* theme variables, and a GitHub link pointing at codbex-hyperion.

Verification

mvn -T 1C clean install -P quick-build, mvn -T 1C formatter:validate, mvn clean install -P unit-tests - all green; every dirigible-* jar in the fat jar at 14.17.0.

On a running instance: /302 /services/web/shell-ide/; /services/ide/java-debug/config and the Debug view both 200; /services/ide/intent/parse, /services/web/builder/ and /services/web/inbox/ all 404; the shell switcher lists no builderShell; the template list offers template-camel-cron-route and template-camel-http-route.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

🤖 Generated with Claude Code

… home

Iapetus is the integrations edition: Apache Camel is the focus, there is no BPM and no
Intent Driven tooling, and its users land in the Workbench rather than on the platform's
Home launchpad.

Version
- codbex-platform-parent 13.6.0 -> 14.17.0 (parents track Dirigible releases 1:1).

Full Java support
- engine-java (in-process javac + the bean container), data-store-java (Java @entity ->
  Hibernate), the api-modules-java SDK, ide-java-lsp (JDT.LS), ide-java-debug (the DAP
  bridge) and the Java / Java Debug views.
- Documented caveat: the SDK exposes org.eclipse.dirigible.sdk.bpm, so
  api-modules-java -> api-bpm -> engine-bpm-flowable puts the BPM engine on the classpath.
  Excluding api-bpm builds and boots but leaves sdk.bpm broken the moment client code
  touches it, so the engine stays and only the BPM tooling is left out (no BPMN editor, no
  Processes perspective, no BPM menus or templates - none of which this edition ever had).

No Intent Driven tooling
- There is no engine-intent, so resources-builder (the conversational Builder shell) is
  excluded from group-ui rather than shipped with nothing behind it. resources-inbox is
  excluded for the same reason: the BPM task inbox has no BPM surface here.

Home is the Workbench
- DIRIGIBLE_HOME_URL=services/web/shell-ide/, overriding the 14.16.0+ default of
  services/web/home/. The launchpad stays reachable at /services/web/home/; only the /
  redirect changes.
- Consequence: upstream's HomepageRedirectIT asserts the platform default and cannot pass
  here, so it leaves the common suite. The edition's own HomePageIT (Workbench welcome view
  on /) guards the override, unchanged.

Camel
- No dependency change was needed: template-camel is an aggregator that already carries
  template-camel-cron-route and template-camel-http-route (verified on a running instance -
  both starters are offered). Annotated as such so nobody adds them again.

UI overrides (forks of upstream files, drifted)
- menu-help: port to the current module shape (ESM + the conditional OpenAPI entry) and
  move translations/ to i18n/, the only folder locales.js scans - the Bulgarian help-menu
  catalog had been dead.
- view-welcome: fix the misspelled `require` form-item flag, point the GitHub link at
  codbex-iapetus instead of codbex-hyperion, and use the BlimpKit theme variables.

Verified: quick-build, formatter:validate and unit tests green; every dirigible jar in the
fat jar resolves at 14.17.0. On a running instance / answers 302 to /services/web/shell-ide/,
the Java debugger config and Debug view answer 200, the intent endpoints, the Builder shell
and the Inbox all 404, the shell switcher lists no builderShell, and the template list
offers both Camel route starters.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.

1 participant