Troubleshooting

org.osgi.framework.BundleException

Cause

If you run DvCliAdaptive as multiple instances without having built the configuration cache first, org.osgi.framework.BundleException is thrown.

Solution

Run only one DvCliAdaptive instance. This builds the configuration cache at

  • <DvDevAdaptive>/configuration/org.eclipse.core.runtime and

  • <DvDevAdaptive>/configuration/org.eclipse.osgi

After that you can run DvCliAdaptive as multiple instances.

If you moved the configuration cache to another folder, DvCliAdaptive builds the cache in that folder instead. See Changed Files in the BSW Package.

Changed Files in the BSW Package

Cause

DvCliAdaptive stores its configuration cache in <BSW Package>/CLI/Core/configuration, next to the executable. Every run updates this folder.

This is a problem if the BSW Package has to stay unchanged, for example if it is shared between several users, shared between several CI jobs, or verified by a checksum.

If the BSW Package is read-only, DvCliAdaptive does not report an error. It moves the configuration cache to the .eclipse folder in your home directory instead. DvCliAdaptive creates one such folder of about 70 MB for each installation path and does not delete it again.

Solution

Use the -configuration argument to keep the configuration cache in a writable folder outside the BSW Package. This also prevents the fallback to your home directory.

Linux

./DvCliAdaptive -configuration <folder> [COMMAND] [ARGS…​]

Windows

.\DvCliAdaptive -configuration <folder> [COMMAND] [ARGS…​]

To apply the setting to every run, add the argument to the DvCliAdaptive.ini file next to the executable. Write the argument and its value on separate lines, before the -vmargs line:

-configuration
<folder>

Give each user and each CI job a folder of its own. Concurrent runs that share one configuration cache can throw org.osgi.framework.BundleException.

Log File in the Working Directory

Cause

Commands that load a model write their log messages to DvCliAdaptive.log in the current working directory. In a CI pipeline this is usually the repository checkout, so the log file ends up in your version control system. DvCliAdaptive appends to the file, which therefore grows with every run.

Solution

Use the --log-file argument to write the log to a file of your choice, outside the working directory.

Linux

./DvCliAdaptive [COMMAND] --log-file=/home/user/logs/example.log

Windows

.\DvCliAdaptive [COMMAND] --log-file="C:\Logs\example.log"

For the other logging arguments, see Basic Options.