Skip to content

fix(build): fix broken step in build system - #59

Closed
gushinetsm wants to merge 1 commit into
rocketride-org:developfrom
gushinetsm:develop
Closed

gushinetsm wants to merge 1 commit into
rocketride-org:developfrom
gushinetsm:develop

Conversation

@gushinetsm

Copy link
Copy Markdown
Contributor

#58

Add a top-level tika:build action that orchestrates the full Java/Tika build pipeline: submodule build, source sync, parallel module builds, and output sync.

Add a top-level tika:build action that orchestrates the full Java/Tika build pipeline: submodule build, source sync, parallel module builds, and output sync.

Made-with: Cursor
@Rod-Christensen

Rod-Christensen commented Feb 27, 2026 •

Copy link
Copy Markdown
Collaborator

Hey Mikhail,

Why do we need the public action? The problem, why it was removed was specifically so it wouldn't be called on a builder buld command. Since it is not always required in the case of the download optimization, it was renamed and is now a dependency of the engine itself.

As with all rules, you can always run any a tion independently -- builder tika:submodule-build.

The.root of the problem really is on the ads script. It should really only reference server:build -- let the server build coordinate its submodules as needed.

I understand the check to make sure the jars are there, but the build change will pull in a bunch of stuff that is not needed.

@gushinetsm

Copy link
Copy Markdown
Contributor Author

Okay, I`ll fix that on ads side

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