Documentation
rte_2x
developPrimary versionrte_2xvuepress-migration
rte_2x
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
  1. Coder devtools - CDT
  2. User guide

Change active webpackage

PreviousValidate the manifest.webpackage fileNextBulk upload of webpackages

Last updated 5 years ago

A cubbles project may contain more than one webpackage. You can use the with all existing webpackages; however, you must indicate which is the current webpackage. You can do it manually in the .workspace file of the webpackages folder of your project; or, you can do it using the _change-activeWebpackage task.

Purpose

To show how to change current active project to be used by the using the _change-activeWebpackage task.

Steps

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

grunt _change-activeWebpackage

Second, a list of the existing webpackages will be prompted. You should choose the webpackage to be used as active by typing its index. The list is similar to the one below:

? Please type the index of your choice to change the activeWebpackage or to CANCEL:  
  1) my-first-webpackage
  2) my-second-webpackage
  3) CANCEL
  Answer:

If you type a wrong index, you would have another chance to type it correctly. If you choose the CANCEL option, the process will finish without making any change.

Outcome

The .workspace file in the webpackages folder will be updated with the selected webpackage, and all the tasks will use it.

CDT
CDT
CDT