To prevent spam users, you can only post on this forum after registration, which is by invitation. If you want to post on the forum, please send me a mail (h DOT m DOT w DOT verbeek AT tue DOT nl) and I'll send you an invitation in return for an account.

Categeries of ProM packages

hverbeekhverbeek Posts: 313
edited December 2016 in - Development
In ProM, we distinguish a number of different categories of ProM packages. This post explains these categories, and what they are good for. Typically, you will start with a Local or Sandbox package, and then move up in the hierarchy through Starter and RunnerUp until the package has become Established.

Local package

  • Local on the machine of the developer.
  • Can only be used by running the package launch file.

Sandbox package

  • Stored in our SVN repository (requires account for repository).
  • Automated build by our continuous build server (Hudson) starts within 24 hours of any commit. You will receive an e-mail if the build fails.
  • Can only be used by running the package launch file.

Starter package

  • Stored in our repository (requires account for repository).
  • Automated build by our continuous build server (Hudson) starts within 12 hours of any commit. You will receive an e-mail if the build fails.
  • Can be released manually by you using Hudson (requires account for Hudson).
  • Can be installed manually in ProM Nightly Build using the ProM Package Manager.

RunnerUp package

  • Stored in our repository (requires account for repository).
  • Automated build by our continuous build server (Hudson) starts within 6 hours of any commit. You will receive an e-mail if the build fails.
  • Can be released manually by you using Hudson (requires account for Hudson).
  • Can be installed manually in ProM Nightly Build using the ProM Package Manager.
  • Is also automatically installed by default in the ProM Nightly Build.
  • Up or out: After one year, a RunnerUp package must be Established.
  • Must use Ivy for package dependencies.
  • May only depend on RunnerUp or Established packages.

Established package

  • Stored in our repository (requires account for repository).
  • Automated build by our continuous build server (Hudson) starts within 3 hours of any commit. You will receive an e-mail if the build fails.
  • Can be released manually by you using Hudson (requires account for Hudson).
  • Can be installed manually in ProM Nightly Build using the ProM Package Manager.
  • Is also automatically installed by default in the ProM Nightly Build.
  • Requires documentation on how to use the package and its plugins.
  • Must use Ivy for package dependencies.
  • May only depend on Established packages.
  • Protection from changes in packages it depends on: 'upstream' changes will be rejected if they would break a 'downstream' Established package.







Post edited by hverbeek on
Sign In or Register to comment.