Bug 1198013 - DevToolsModules now safe to call multiple times. r=mratcliffe draft
authorJ. Ryan Stinnett <jryans@gmail.com>
Fri, 03 Nov 2017 12:38:05 -0500
changeset 692873 92c16d50f60a88fd6ae42a8ec0fab09b657831bb
parent 692714 4ada8f0d5cc011af4bc0f4fadbb25ea3e1e62bfc
child 738880 9b7782ccf4c622611a76023ef3fbaf301f1ed86b
push id87634
push userbmo:jryans@gmail.com
push dateFri, 03 Nov 2017 17:41:32 +0000
reviewersmratcliffe
bugs1198013
milestone58.0a1
Bug 1198013 - DevToolsModules now safe to call multiple times. r=mratcliffe MozReview-Commit-ID: 2wg78JE6Cb7
devtools/templates.mozbuild
--- a/devtools/templates.mozbuild
+++ b/devtools/templates.mozbuild
@@ -9,21 +9,17 @@ def DevToolsModules(*modules):
     '''Installs JS modules at a resource:// path that corresponds directly to
     their source tree location.
 
     For this to work as intended, a moz.build file should be placed in each
     source directory which uses this template to install only the JS files in
     its own directory.  Subdirectories should use their own moz.build.
 
     By following this pattern, there's less magic to require() and resource://
-    paths, since they now match the source tree.
-
-    Currently `DevToolsModules` can only be called once per moz.build, so we
-    build a list manually above.  Bug 1198013 tracks fixing this to make it more
-    like other moz.build constructs.'''
+    paths, since they now match the source tree.'''
 
     for m in modules:
         if '/' in m:
             error('DevToolsModules must be used from the same directory as ' +
                   'the files to be installed.')
 
     # jar.mn manifest files are typically used to install files to chrome
     # locations.  Instead of doing this, use this DevToolsModules syntax via