Opened 11 years ago

Closed 8 years ago

#8062 closed defect (invalid)

Error in custom build with 1.2.1

Reported by: ssambi Owned by: James Burke
Priority: high Milestone: future
Component: BuildTools Version: 1.2.1
Keywords: Cc:
Blocked By: Blocking:

Description

I've got an error in my custom build with 1.2.1 version. The error is the following:

release:  Interning strings for : ../../../release/dojo/dijit/_TimePicker.js
release:      ..\..\..\release\dojo/dijit/templates/TimePicker.html
js: "jslib/i18nUtil.js#59(eval)", line 1: uncaught JavaScript runtime exception:
 SyntaxError: missing name after . operator
js: dijit..........release.dojo.dijit.form
js: ........^

I've attached my profile file, the parameters of build.bat and the full log. I've got the same error with 1.2.0

Attachments (3)

full_log.txt (10.0 KB) - added by ssambi 11 years ago.
Full log
genera.bat (198 bytes) - added by ssambi 11 years ago.
Batch to run build.bat with parameters
sellercenter.profile.js (939 bytes) - added by ssambi 11 years ago.
My profile file

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by ssambi

Attachment: full_log.txt added

Full log

Changed 11 years ago by ssambi

Attachment: genera.bat added

Batch to run build.bat with parameters

Changed 11 years ago by ssambi

Attachment: sellercenter.profile.js added

My profile file

comment:1 Changed 11 years ago by James Burke

Milestone: tbdfuture

This looks like a bug in how releaseDir is processed to figure out the module names to use for i18n bundles.

As a workaround, you might try using a path without . characters for releaseDir. If that does not work, then have the build get generated in the default location (as a sibling to dojo directory) and copy the files out of there.

comment:2 Changed 11 years ago by James Burke

BTW, thank you for the great bug report!

comment:3 Changed 8 years ago by Adam Peller

Resolution: invalid
Status: newclosed

I wonder if it has anything to do with the backslashes. Build system has been completely replaced since this report was filed, and a workaround was suggested. Please reopen if you still have problems.

Note: See TracTickets for help on using tickets.