Defines when/how resolving is done to calculate the -runbundles

  • Example: -resolve: '-resolve manual

  • Values: manual,auto,beforelaunch,batch,cache,never

  • Pattern: (manual|auto|beforelaunch|batch)

Directives

  • manual Bundles are resolved manually using the Resolve button. The -runbundles list is never modified automatically.

    • Values: manual

    • Pattern: \Qmanual\E

  • auto The resolver runs automatically on every save, replacing -runbundles with the resolved result. Manual edits to -runbundles will be overwritten.

    • Values: auto

    • Pattern: \Qauto\E

  • beforelaunch The resolver runs automatically before each launch, updating -runbundles with the resolved result.

    • Values: beforelaunch

    • Pattern: \Qbeforelaunch\E

  • batch The resolver runs before launching in batch mode (e.g. Gradle) but not in IDE mode (e.g. Eclipse). In IDE mode the -runbundles list must be managed manually.

    • Values: batch

    • Pattern: \Qbatch\E

  • cache The resolver runs when -runbundles are needed, unless a cache file (same name prefixed with ‘.’) is newer than the project and workspace.

    • Values: cache

    • Pattern: \Qcache\E

  • never Resolving never takes place automatically. The -runbundles list must be managed manually. Attempting to resolve manually will result in an error.

    • Values: never

    • Pattern: \Qnever\E



The bnd workspace can use a resolver to calculate the content of the -runbundles instruction based on a set of initial requirements. The bndtools GUI can manually resolve the initial requirements but through the -resolve instruction it is possible to calculate the -runbundles when the file is saved or just before the -runbundles are used in the launch.

The values are:

  • manual – It is up to the user to resolve the initial requirements
  • auto – Whenever the initial requirements are saved, the resolver will be used to set new -runbundles
  • beforelaunch – Calculate the -runbundles on demand. This ignores the value of the -runbundles and runs the resolver. The results of the resolver are cached. This cache works by creating a checksum over all the properties of the project.
  • batch – When running in batch mode, the run bundles will be resolved. In all other modes this will only resolve when the -runbundles are empty.
  • cache – Will use a cache file in the workspace cache. If that file is stale relative to the workspace or project or it does not exist, then the bnd(run) file will be resolved and the result is stored in the cache file.
  • never – If anybody tries to resolve , the process will throw an UnsupportedOperationException. This is intended for manually curated runbundles or where a base file is resolved and other files include them an add some additional instructions. The Excepetion is meant as a clear warning to any developer accidentally resolving the -runbundles.

Example 

-resolve beforelaunch