documentation updates.

icfnext · May 16, 2017 · 7b65f30 · 7b65f30
1 parent 4484249
commit 7b65f30
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 11 deletions.
diff --git a/README.md b/README.md
@@ -28,6 +28,12 @@ Additional build profiles may be added in the project's pom.xml to support deplo
 
 AEM 6.0 no longer allows vanity paths for pages in /etc by default.  To enable access to the Groovy Console from /groovyconsole as in previous versions, the Apache Sling Resource Resolver Factory OSGi configuration must be updated to allow vanity paths from /etc.  The Groovy Console Configuration Service can then be updated to enable the vanity path if so desired.
 
+## Excluding the Groovy OSGi Bundle
+
+If your AEM instance has multiple applications using Groovy and the `groovy-all` bundle is already deployed, you can exclude this bundle from the Groovy Console package build with the `exclude-groovy-bundle` Maven profile.  This should prevent issues with conflicting Groovy versions at runtime.
+
+    mvn install -P local,exclude-groovy-bundle
+
 ## Context Path Support
 
 If you are running AEM with a context path, set the Maven property `aem.context.path` during installation.

diff --git a/pom.xml b/pom.xml
@@ -11,12 +11,12 @@
     <groupId>com.icfolson.aem.groovy.console</groupId>
     <artifactId>aem-groovy-console</artifactId>
     <packaging>jar</packaging>
-    <version>11.0.0-SNAPSHOT</version>
+    <version>11.0.0</version>
     <name>AEM Groovy Console</name>
     <description>
-        The AEM Groovy Console provides an interface for running Groovy scripts in the AEM (Adobe CQ) container. Scripts
-        can be created to manipulate content in the JCR, call OSGi services, or execute arbitrary code using the AEM,
-        Sling, or JCR APIs.
+        The AEM Groovy Console provides an interface for running Groovy scripts in the AEM container. Scripts can be
+        created to manipulate content in the JCR, call OSGi services, or execute arbitrary code using the AEM, Sling,
+        or JCR APIs.
     </description>
 
     <organization>

diff --git a/src/main/content/jcr_root/etc/clientlibs/groovyconsole/js/console.js b/src/main/content/jcr_root/etc/clientlibs/groovyconsole/js/console.js
@@ -153,18 +153,13 @@ var GroovyConsole = function () {
 
                     $('#run-script-text').text('Running...');
 
-                    var async = $('input[name="async"]').is(':checked');
-
                     $.post(CQ.shared.HTTP.getContextPath() + '/bin/groovyconsole/post.json', {
                         script: script,
-                        // async: async,
                         data: dataEditor.getSession().getValue()
                     }).done(function (response) {
-                        if (!async) {
-                            GroovyConsole.showResult(response);
-                        }
+                        GroovyConsole.showResult(response);
                     }).fail(function (jqXHR) {
-                        if (jqXHR.status == 403) {
+                        if (jqXHR.status === 403) {
                             GroovyConsole.showError('You do not have permission to run scripts in the Groovy Console.');
                         } else {
                             GroovyConsole.showError('Script execution failed.  Check error.log file.');