Cross Domain build exception

[vincentastek]

Hi,

I'm trying to make a cross domain build of dojo using the following command :

build.bat profile=toto action=clean,release loader=xdomain xdDojoPath=​http://myurl.com/dojo optimize= layerOptimize=

I got the following exception :

js: uncaught JavaScript? runtime exception: TypeError?: Cannot read property "index" from null

I tracked this error and it happens when build.js calls (l.171) :

fileContents = buildUtilXd.setXdDojoConfig(fileContents, kwArgs.xdDojoPath,logger);

The error seems to happen in buildUtil.js in the following section (l.17) :

var match = fileContents.match(/(dojo\.registerModulePath\s*=\s*function.*\{)/);

Find the next two } braces and in inject code after that. var endIndex = fileContents.indexOf("}", match.index); endIndex = fileContents.indexOf("}", endIndex + 1); if(fileContents.charAt(endIndex + 1) == ";"){

endIndex += 1;

} endIndex +=1;

I'm attaching the complete log output and my profile file. Please provide any help.

Vincent

[vincentastek]

Profile file

[vincentastek]

Output Log

[vincentastek]

More infos :

Sounds like it happens on afdojo.xd.js treatment (dojo.xd.js treatment is ok).

afdojo.xd.js doesn't exist before the build. afdojo is the name I specified as my custom layer in the profile file. It seems like the function searches for a dojo.registerModulePath pattern that doesn't exist.

Am I missing something ?

[James Burke]

Yeah, there is a bug in the build code. If you change the name to afmojo.js, the build works. I think it has to do with how the code tries to assume a config path based on pathing info.

[dante]

punting, though recently opened. tdb -> future for 1.3b

[ben hockey]

can we close this since in 1.7 we have a completely new build tool?

if there's no response within 14 days this ticket will automatically close.

[trac-o-bot]

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!