Documentation
vuepress-migration
developPrimary versionrte_2xvuepress-migration
vuepress-migration
developPrimary versionrte_2xvuepress-migration
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • Purpose
  • Steps
  • Outcome
  • The npm module version
  1. Coder devtools - CDT
  2. User guide

Update the RTE version of a webpackage

PreviousRelease a webpackageNextPrepare a webpackage to be released

Last updated 5 years ago

Sometimes you may be interested in updating the used RTE version of a webpackage. That is, to refactor the demo, docs and manifest files. The offers the _webpackage-updateRte task to perform that process automatically.

Purpose

To describe how to update the RTE used by the components of a webpackage using the _webpackage-updateRte task.

Steps

First, you should run the task within the CDT folder (normally it is called devtools) as follows:

grunt  _webpackage-updateRte

Second, you should type the version to be used. It should have the proper format; i.e., a one, two or three dot-separated digits, with a -SNAPSHOT suffix for developing versions: For example, 2.4, 3.0.0 or 3.0.0-SNAPSHOT

Outcome

The dependencies and runnables of each artifact in the manifest.webpackage file will be refactored to use the new RTE version.

Note that if you choose to update the RTE to 3.0.0 or above, the runnables will be fixed. However, you would have to fix the resources of all elementary components in the webpackage to meet RTE@3.x requirements.

The npm module version

You can use an npm module that serves the same purposes called . The module can be used from the command line or in a node script.

CDT
cubx-webpackage-rte-update