require.js file now being written to project root

[ajmichels]

I am just creating this issue since it doesn't appear to exist yet. I am not sure what the best solution is. I am going to try to summarize the problem as best as I can.

As reported in gruntjs/grunt-contrib-jasmine#255, an update was made to gruntjs/grunt-contrib-jasmine which has caused the location of temporary files to change. This means that when _SpecRunner.html (a generated files) is executed it cannot locate the require.js file and task fails.

This issue results in output similar to this:

>> ReferenceError: Can't find variable: require at
>> http:/127.0.0.1:8001/_SpecRunner.html:30 global code
>> ReferenceError: Can't find variable: require at
>> http:/127.0.0.1:8001/_SpecRunner.html:46 global code
>> ReferenceError: Can't find variable: require at
>> http:/127.0.0.1:8001/_SpecRunner.html:147 launchTest

Myself and others have found that reverting grunt-contrib-jasmine to version 1.0.3 resolves the issue, however this seems like a far from ideal solution and is by no means a permanent one.

[prantlf]

I opened #95 to fix this. I use a different way to copy files to temp directory, compatible with both older and newer versions of grunt-contrib-jasmine than 1.2.0.

These files are copied to the project root instead of to the temp directory with the rest of Jasmine files. grunt-contrib-jasmine broke their interface between 1.0.3 and 1.2.0 without increasing the major version number. (!!!) This should be discussed with grunt-contrib-jasmine developers.

[psharkin]

@prantlf Is there any chance #95 will be merged to master any time soon?