Workspace configuration export retains absolute file paths—how to make it portable?

Workspace configuration export retains absolute file paths

When creating a repeatable development environment, the DBeaver workspace is often exported and mounted into a Docker container. The exported settings, however, contain absolute paths to the connection metadata files stored under the .metadata/.plugins/org.eclipse.core.runtime/.settings directory. This makes the configuration brittle: the container’s filesystem layout differs from the host, causing connection resolution failures.

Additionally, the network timeout for JDBC connections defaults to driver‑specific values, and there is no documented global override that applies to all data sources. This limits the ability to enforce consistent timeout policies across a team’s shared workspace.

Given these constraints, the following questions remain:

• Is there a built‑in mechanism or export option that rewrites absolute paths to relative ones, or a post‑export script that can standardize them?
• Does DBeaver provide a configuration setting or plugin that allows a global network timeout to be applied to all JDBC connections regardless of driver defaults?