Handle New Library Releases or Major Updates
When updates to custom or third party libraries are far reaching or not backwards compatible with existing versions, updates can cause errors in the dependent pluggable views, views or apps that use those views. See
Library Versions and Dependencies for more information on library dependencies.
The best practice, in this case, is to import new releases or major updates as a new library, using a different library ID. This allows you to manage how dependent pluggable views, views and apps migrate to this new release or update.
For new releases of third-party libraries, you can simply download the library and add it to
MashZone NextGen or add a new library that points to the externally hosted library. See
Creating Pluggable Views or Libraries for the basic steps. Then update any pluggable views, if any, that should use this new release.
For major updates to pluggable views or pluggable libraries with local code for your organization:
This downloads all resources for the current default version of the pluggable library you requested.
2. Change the root library name to a new ID and update the properties file or <target> in the Ant build.xml file to use this new ID.
3. Update the code as needed.
4. Then import the new pluggable library or view with the importLib command or your Ant build.
For importLib:
a. Open a command window and move to the MashZoneNG-install/prestocli/bin folder.
b. Enter this command:
padmin importLib -d path-to-library-root-folder -o -u username -w password
Add views based on this new pluggable view library and update apps, as needed.