starred/cloudbeaver

Fork 0

mirror of https://github.com/dbeaver/cloudbeaver.git synced 2026-03-04 08:52:27 -05:00

CloudBeaver build fails due to incompatible DBeaver version #970

New issue

Open

opened 2026-03-04 11:27:19 -05:00 by deekerman · 3 comments

deekerman commented

2026-03-04 11:27:19 -05:00

Owner

Originally created by @maryam4s26 on GitHub (Sep 4, 2025).

Description

When building CloudBeaver using the current build.sh script, the build fails with errors like:

CmdProcessResult cannot be resolved
import org.jkiss.dbeaver.model.cli.CmdProcessResult;

The backend build script build-backend.sh always clones the latest master branches of the DBeaver repositories (dbeaver, dbeaver-common, dbeaver-jdbc-libsql):

[ ! -d dbeaver ] && git clone --depth 1 https://github.com/dbeaver/dbeaver.git
[ ! -d dbeaver-common ] && git clone --depth 1 https://github.com/dbeaver/dbeaver-common.git
[ ! -d dbeaver-jdbc-libsql ] && git clone --depth 1 https://github.com/dbeaver/dbeaver-jdbc-libsql.git

CloudBeaver is tightly coupled with specific DBeaver versions, so using a mismatched DBeaver version breaks the build.

Proposed solution
Update the build script to clone the DBeaver version that matches the CloudBeaver version being built, instead of always pulling the latest master. This will ensure compatibility and successful builds.

Additional notes
• The compilation fails specifically in:
cloudbeaver/server/bundles/io.cloudbeaver.model/src/io/cloudbeaver/model/cli/CloudBeaverInstanceServer.java
• The error is caused by the missing class:

import org.jkiss.dbeaver.model.cli.CmdProcessResult;
link.

This class was removed in the newer DBeaver versions.

Steps to reproduce

Clone CloudBeaver 25.1.2.
Run the build script:
./deploy/build.sh
Observe compilation errors related to CmdProcessResult.

Expected/Desired Behavior

The build should complete successfully without compilation errors.

CloudBeaver Version

25.1.2

Additional context

No response

Originally created by @maryam4s26 on GitHub (Sep 4, 2025). ### Description When building CloudBeaver using the current [build.sh](https://github.com/dbeaver/cloudbeaver/blob/devel/deploy/build.sh) script, the build fails with errors like: ```bash CmdProcessResult cannot be resolved import org.jkiss.dbeaver.model.cli.CmdProcessResult; ``` The backend build script [build-backend.sh](https://github.com/dbeaver/cloudbeaver/blob/devel/deploy/build-backend.sh) always clones the latest master branches of the DBeaver repositories (dbeaver, dbeaver-common, dbeaver-jdbc-libsql): ```bash [ ! -d dbeaver ] && git clone --depth 1 https://github.com/dbeaver/dbeaver.git [ ! -d dbeaver-common ] && git clone --depth 1 https://github.com/dbeaver/dbeaver-common.git [ ! -d dbeaver-jdbc-libsql ] && git clone --depth 1 https://github.com/dbeaver/dbeaver-jdbc-libsql.git ``` CloudBeaver is tightly coupled with specific DBeaver versions, so using a mismatched DBeaver version breaks the build. **Proposed solution** Update the build script to clone the DBeaver version that matches the CloudBeaver version being built, instead of always pulling the latest master. This will ensure compatibility and successful builds. **Additional notes** • The compilation fails specifically in: `cloudbeaver/server/bundles/io.cloudbeaver.model/src/io/cloudbeaver/model/cli/CloudBeaverInstanceServer.java ` • The error is caused by the missing class: `import org.jkiss.dbeaver.model.cli.CmdProcessResult; ` [link](https://github.com/dbeaver/cloudbeaver/blob/release_25_1_2/server/bundles/io.cloudbeaver.model/src/io/cloudbeaver/model/cli/CloudBeaverInstanceServer.java#L23). This class was removed in the newer DBeaver versions. ### Steps to reproduce 1. Clone CloudBeaver 25.1.2. 2. Run the build script: `./deploy/build.sh` 3. Observe compilation errors related to CmdProcessResult. ### Expected/Desired Behavior The build should complete successfully without compilation errors. ### CloudBeaver Version 25.1.2 ### Additional context _No response_

deekerman added the

deployment

label

2026-03-04 11:27:19 -05:00

deekerman commented

2026-03-04 11:27:28 -05:00

Author

Owner

@dariamarutkina commented on GitHub (Sep 4, 2025):

Hello, @maryam4s26 !

Could you please update your repositories to the latest state?

In the dbeaver repository, run git pull.
In the cloudbeaver repository, switch to the devel branch and run git pull as well.

After that, try rebuilding CloudBeaver - the error should be resolved 🦫

@dariamarutkina commented on GitHub (Sep 4, 2025): Hello, @maryam4s26 ! Could you please update your repositories to the latest state? 1. In the **dbeaver** repository, run `git pull`. 2. In the **cloudbeaver** repository, switch to the `devel` branch and run `git pull` as well. After that, try rebuilding CloudBeaver - the error should be resolved 🦫

deekerman commented

2026-03-04 11:27:36 -05:00

Author

Owner

@maryam4s26 commented on GitHub (Sep 4, 2025):

Hello, @maryam4s26 !

Could you please update your repositories to the latest state?

In the dbeaver repository, run git pull.

In the cloudbeaver repository, switch to the devel branch and run git pull as well.

After that, try rebuilding CloudBeaver - the error should be resolved 🦫

Thanks @dariamarutkina for the suggestion! 😅

This seems more like a temporary workaround rather than a proper fix. The root cause is that the CloudBeaver build script always pulls the latest master branches of DBeaver, which may not be compatible with the CloudBeaver version we’re building.

I specifically want to use a fixed DBeaver version, so constantly updating to the latest master is not ideal. A proper solution would be to either target a specific DBeaver release in the CloudBeaver repo or specify the exact dependency versions in the backend build file.

As a proper solution, we can update the build-backend.sh script to clone specific branches of the DBeaver repositories that match the CloudBeaver version we are building. For example:

DBEAVER_BRANCH="release_25_1_2"

[ ! -d dbeaver ] && git clone --branch $DBEAVER_BRANCH --depth 1 https://github.com/dbeaver/dbeaver.git
[ ! -d dbeaver-common ] && git clone --branch $DBEAVER_BRANCH --depth 1 https://github.com/dbeaver/dbeaver-common.git
[ ! -d dbeaver-jdbc-libsql ] && git clone --branch $DBEAVER_BRANCH --depth 1 https://github.com/dbeaver/dbeaver-jdbc-libsql.git

This ensures that the dependencies are consistent with the CloudBeaver version, avoiding missing classes or 404 icon issues in production.

To properly address this issue, either the CloudBeaver documentation should clearly specify the compatible DBeaver versions, or the build-backend.sh script should be updated to always use the correct versions. This will ensure consistent builds and prevent missing dependencies or broken features.

@maryam4s26 commented on GitHub (Sep 4, 2025): > Hello, [@maryam4s26](https://github.com/maryam4s26) ! > > Could you please update your repositories to the latest state? > > 1. In the **dbeaver** repository, run `git pull`. > 2. In the **cloudbeaver** repository, switch to the `devel` branch and run `git pull` as well. > > After that, try rebuilding CloudBeaver - the error should be resolved 🦫 Thanks @dariamarutkina for the suggestion! 😅 This seems more like a temporary workaround rather than a proper fix. The root cause is that the CloudBeaver build script always pulls the latest master branches of DBeaver, which may not be compatible with the CloudBeaver version we’re building. I specifically want to use a fixed DBeaver version, so constantly updating to the latest master is not ideal. A proper solution would be to either target a specific DBeaver release in the CloudBeaver repo or specify the exact dependency versions in the backend build file. As a proper solution, we can update the build-backend.sh script to clone specific branches of the DBeaver repositories that match the CloudBeaver version we are building. For example: ```sh DBEAVER_BRANCH="release_25_1_2" [ ! -d dbeaver ] && git clone --branch $DBEAVER_BRANCH --depth 1 https://github.com/dbeaver/dbeaver.git [ ! -d dbeaver-common ] && git clone --branch $DBEAVER_BRANCH --depth 1 https://github.com/dbeaver/dbeaver-common.git [ ! -d dbeaver-jdbc-libsql ] && git clone --branch $DBEAVER_BRANCH --depth 1 https://github.com/dbeaver/dbeaver-jdbc-libsql.git ``` This ensures that the dependencies are consistent with the CloudBeaver version, avoiding missing classes or 404 icon issues in production. To properly address this issue, either the CloudBeaver documentation should clearly specify the compatible DBeaver versions, or the build-backend.sh script should be updated to always use the correct versions. This will ensure consistent builds and prevent missing dependencies or broken features.

deekerman commented

2026-03-04 11:27:37 -05:00

Author

Owner

@dariamarutkina commented on GitHub (Sep 4, 2025):

Thank you for the feature suggestion! 🙏
You’re right, it would be helpful to adjust the script so it uses the DBeaver release branches for each CloudBeaver version 🦫

@dariamarutkina commented on GitHub (Sep 4, 2025): Thank you for the feature suggestion! 🙏 You’re right, it would be helpful to adjust the script so it uses the DBeaver release branches for each CloudBeaver version 🦫