Update profile file to reflect changes in rc2 & use smarter selector …

…engine loading mechanism.

profiles/main.profile.js

@@ -2,8 +2,8 @@
  * Build profiles look mostly the same in Dojo 1.7 as they do in previous versions of the toolkit.
  */
 dependencies = {
-    // First cleans the dist directory of existing code, then builds a new release.
-    action: 'clean,release',
+    // Builds a new release.
+    action: 'release',
 
     // Strips all comments from CSS files.
     cssOptimize: 'comments',
@@ -20,17 +20,17 @@ dependencies = {
     // Strips all calls to console functions within the code.
     stripConsole: 'all',
 
+    // The default selector engine is not included by default in a dojo.js build in order to make mobile builds
+    // smaller. We add it back here to avoid that extra HTTP request.
+    selectorEngine: 'acme',
+
     // Builds can be split into multiple different JavaScript files called "layers". This allows applications to
     // defer loading large sections of code until they are actually required. Note that, at the moment, module IDs
     // in "dependencies" are still written using dots instead of slashes.
     layers: [
-        // The default selector engine is not included by default in a dojo.js build in order to make mobile builds
-        // smaller. We add it back here to avoid that extra HTTP request.
-        { name: 'dojo.js', dependencies: [ 'dojo.selector.acme' ] },
-
         // This is our main application layer. This layer will normally contain most or all of your application code.
         { name: '../app/main.js', dependencies: [ 'app.main' ] },
-        
+
         // In the demo application, we conditionally require app/Dialog on the client-side, so we're building a
         // separate layer containing just that client-side code.
         { name: '../app/Dialog.js', dependencies: [ 'app.Dialog' ] }