Release 6.0.0

Author: benm071

README.md

@@ -1,4 +1,4 @@
-# @oracle/ojet-cli 5.2.0
+# @oracle/ojet-cli 6.0.0
 
 ## About the module
 This module contains a command line interface for Oracle JET web and hybrid mobile application development.
@@ -64,7 +64,7 @@ Or view help on adding a plugin:
 ojet help add plugin
 ```
 
-For more information on the Oracle JET CLI, refer to the [Oracle JET Developers Guide](http://www.oracle.com/pls/topic/lookup?ctx=jet520&id=homepage).
+For more information on the Oracle JET CLI, refer to the [Oracle JET Developers Guide](http://www.oracle.com/pls/topic/lookup?ctx=jet600&id=homepage).
 
 ## [Contributing](https://github.com/oracle/ojet-cli/tree/master/CONTRIBUTING.md)
 Oracle JET is an open source project.  Pull Requests are currently not being accepted. See [CONTRIBUTING](https://github.com/oracle/ojet-cli/tree/master/CONTRIBUTING.md) for details.

RELEASENOTES.md

@@ -1,46 +1,57 @@
-## Release Notes for ojet-cli ##
-
-### 5.2.0
-* Cordova 8 may cause very slow performance during build and serve.  You may wish to consider downgrading to Cordova 7 if this is an issue.
-
-### 5.1.0
-When using Cordova-Android 7.0.0+, users may encounter an error like:
-
-ENOENT: no such file or directory, open ‘App\hybrid\platforms\android\res\xml\config.xml’
-
-This is because Cordova changed the Android project file structure, and some third-party plugins/tools are not updated yet.
-The error is harmless.  Users can also choose to downgrade to Cordova-Android 6.4.0 to completely avoid the issue. 
-
-More information is in the Cordova-Android 7.0.0 release note: 
-
-https://cordova.apache.org/announcements/2017/12/04/cordova-android-7.0.0.html
-
-### 5.0.0
-* The main-release-paths.json file has been replaced by the path-mapping.json file in templates used to scaffold applications
-* As a continued effort toward abstraction of direct library calls in the JET CLI, the direct use of yeoman and grunt will be removed in the JET v7.0.0 release.  A new hooks API will be provided to allow for customization of tasks.
-
-### 4.2.0
-* No changes
-
-### 4.1.0
-* If JET images are altered, they will be repackaged into the JET sprite files
-
-### 4.0.0
-* Moved module into @oracle scope, changing the name to @oracle/ojet-cli
-* Added 'ojet create component' to scaffold a composite component based on a template
-* Due to a [known issue](https://github.com/phonegap/ios-deploy/issues/292) in the ios-deploy module, serving an app to an iOS device may fail to launch the app with error code 253. Try upgrading to ios-deploy@1.9.2, restarting your device and  reconnecting the USB cable.  Otherwise, launch the app manually.
-* Due to a [known issue](https://github.com/phonegap/ios-deploy/issues/275) in the ios-deploy module, serving an app to an iOS device may fail to launch the app with error code 1.  Try signing the app with developer credentials rather than distribution credentials.  Otherwise, launch the app manually.
-* Updated the help descriptions
-
-### 3.2.0
-* Changed 'ojet add theme' to 'ojet create theme' for consistency
-* Added 'ojet clean' to clean build output from an app
-* Added 'ojet strip' to strip all non source-code from an app
-* Updated the help descriptions
-
-### 3.1.0
-* Changed the syntax to specify the command first, such as 'ojet list plugins' rather than 'ojet plugins list'
-* Updated the help descriptions 
-
-### 3.0.0
-* Initial release
+## Release Notes for ojet-cli ##
+
+### 6.0.0
+
+* Deprecation of "ojet add sass" command.  JET is moving to the use of CSS variables for theming, and as a result, will remove the use of SASS in a future release.
+* On Cordova v7 or v8: A change to the Android Cordova platform location of its config.xml file may result in an "platform.json not found" or "config.xml not found" error messages when you install the latest Cordova version. This will not prevent you from running ojet serve android, but messages returned by ojet serve may appear different from a previous version of Cordova.
+* The current ojet-cli supports 'ojet add windows' but not with a version.  It will install the windows version that comes with the installed Cordova.
+
+If you need a specific version, do the following:
+
+1. cd hybrid
+2. cordova platform add windows@latest
+
+### 5.2.0
+* Cordova 8 may cause very slow performance during build and serve.  You may wish to consider downgrading to Cordova 7 if this is an issue.
+
+### 5.1.0
+When using Cordova-Android 7.0.0+, users may encounter an error like:
+
+ENOENT: no such file or directory, open ‘App\hybrid\platforms\android\res\xml\config.xml’
+
+This is because Cordova changed the Android project file structure, and some third-party plugins/tools are not updated yet.
+The error is harmless.  Users can also choose to downgrade to Cordova-Android 6.4.0 to completely avoid the issue. 
+
+More information is in the Cordova-Android 7.0.0 release note: 
+
+https://cordova.apache.org/announcements/2017/12/04/cordova-android-7.0.0.html
+
+### 5.0.0
+* The main-release-paths.json file has been replaced by the path-mapping.json file in templates used to scaffold applications
+* As a continued effort toward abstraction of direct library calls in the JET CLI, the direct use of yeoman and grunt will be removed in the JET v7.0.0 release.  A new hooks API will be provided to allow for customization of tasks.
+
+### 4.2.0
+* No changes
+
+### 4.1.0
+* If JET images are altered, they will be repackaged into the JET sprite files
+
+### 4.0.0
+* Moved module into @oracle scope, changing the name to @oracle/ojet-cli
+* Added 'ojet create component' to scaffold a composite component based on a template
+* Due to a [known issue](https://github.com/phonegap/ios-deploy/issues/292) in the ios-deploy module, serving an app to an iOS device may fail to launch the app with error code 253. Try upgrading to ios-deploy@1.9.2, restarting your device and  reconnecting the USB cable.  Otherwise, launch the app manually.
+* Due to a [known issue](https://github.com/phonegap/ios-deploy/issues/275) in the ios-deploy module, serving an app to an iOS device may fail to launch the app with error code 1.  Try signing the app with developer credentials rather than distribution credentials.  Otherwise, launch the app manually.
+* Updated the help descriptions
+
+### 3.2.0
+* Changed 'ojet add theme' to 'ojet create theme' for consistency
+* Added 'ojet clean' to clean build output from an app
+* Added 'ojet strip' to strip all non source-code from an app
+* Updated the help descriptions
+
+### 3.1.0
+* Changed the syntax to specify the command first, such as 'ojet list plugins' rather than 'ojet plugins list'
+* Updated the help descriptions 
+
+### 3.0.0
+* Initial release

config.js

@@ -133,10 +133,17 @@ const config = {
             'ojet build app android --release',
             'ojet build ios --device --build-config=./buildConfig.json --theme=myCustomTheme',
             'ojet build web --theme=alta:android',
-            'ojet build windows --platform-options "--archs=\\"x86 x64 arm\\""'
+            'ojet build windows --platform-options="--archs=\\"x86 x64 arm\\""'
+          ]
+        },
+        component: {
+          description: 'Builds an optimized component for the specified component name',
+          parameters: 'component name',
+          examples: [
+            'ojet build component demo-card'
           ]
         }
-      },
+      }
     },
     clean: {
       description: 'Cleans build output from a JET app',
@@ -216,6 +223,12 @@ const config = {
           parameters: '<component-name>',
           examples: ['ojet create component demo-card']
         },
+        pack: {
+          aliases: ['packs'],
+          description: 'Creates a pack with the specified name in an existing app, or creates a pack with a shell app',
+          parameters: '<pack-name>',
+          examples: ['ojet create pack component demo-pack']
+        },
         theme: {
           aliases: ['themes'],
           description: 'Creates a custom theme with the specified name',
@@ -274,6 +287,9 @@ const config = {
               description: 'Specify the pack name',
               parameters: '<pack_name>'
             },
+            release: {
+              description: 'Whether to publish the specified component with a release build'
+            }
           },
           examples: [
             'ojet publish component flipcard'
@@ -347,6 +363,11 @@ const config = {
         exchange: {
           description: 'Searches for a component in the exchange based on the specified keyword',
           parameters: '<keyword>',
+          options: {
+            versions: {
+              description: 'Lists all available versions'
+            }
+          },
           examples: [
             'ojet search exchange flip-card',
             'ojet search exchange flip-card dv-gantt'
@@ -420,13 +441,13 @@ const config = {
             destination: {
               description: 'Specify the destination for serving the app',
               parameters: 'device[:<device_name>]|emulator[:<emulator_name>]|' + // eslint-disable-line
-                newLine + ' browser[:chrome|:firefox|:edge|:ie|:opera|:safari]|server-only',
+                newLine + ' browser[:chrome|:firefox|:edge|:ie|:safari]|server-only',
               default: 'emulator' + // eslint-disable-line
                 newLine + 'Default browser: chrome'
             },
             browser: {
               description: 'Shortcut for --destination=browser',
-              parameters: '[chrome|firefox|edge|ie|opera|safari]',
+              parameters: '[chrome|firefox|edge|ie|safari]',
               default: 'chrome'
             },
             device: {

lib/scopes/app.js

@@ -15,8 +15,8 @@ const path = require('path');
 const env = require('yeoman-environment').createEnv();
 
 // Oracle
+const config = require('../../config');
 const CONSTANTS = require('../utils.constants');
-const component = require('./component');
 const paths = require('../utils.paths');
 const pckg = require('../../package.json');
 const tooling = require('../tooling');
@@ -142,7 +142,9 @@ function _addComponents() {
   Object.keys(composites).forEach((key) => {
     components.push(`${key}@${composites[key]}`);
   });
-  return component.add(components);
+
+  const toolingModule = utils.loadTooling();
+  return toolingModule.add(config.tasks.add.scopes.component.name, components);
 }
 
 /**