Release a webpackage
Last updated
Last updated
When releasing a webpackage to need to:
Check if all dependencies are not under development
Update the current version to a fixed version; i.e., without the -SNAPSHOT
suffix
Upload the webpackage to a store
Update the current version to a valid next development version, since no changes can be uploaded to fixed versions
The offers you the +webpackage-release
task to release a webpackage. Actually, this task uses three other tasks to perform each step:
The task to perform steps 1. and 2.
The task to perform step 3.
The to perform step 4.
You should run the task within the CDT folder (normally it is called devtools) as follows:
Then, each task will be run in the order presented above.
Click on the links provided above for each subtask to see further details about each step.
Your webpackage will be uploaded to a store with a fixed version and the manifest.webpackage
file will end up with the correct next development version.