You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ripple.apache.org by "Brent Lintner (JIRA)" <ji...@apache.org> on 2013/07/08 15:37:50 UTC

[jira] [Commented] (RIPPLE-32) Does not work on Windows

    [ https://issues.apache.org/jira/browse/RIPPLE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13701999#comment-13701999 ] 

Brent Lintner commented on RIPPLE-32:
-------------------------------------

Fixed. In next with: 1ebd828b38ee0d7fa8333fa956b8fe32132dd9be

Considering the circumstances, one of us should tag master so that package
can be in working order for Cordova (until we have official releases). I
volunteer.

+/-?






-- 
Brent Lintner

                
> Does not work on Windows
> ------------------------
>
>                 Key: RIPPLE-32
>                 URL: https://issues.apache.org/jira/browse/RIPPLE-32
>             Project: Apache Ripple
>          Issue Type: Bug
>         Environment: Windows 7, possibly Windows 8
>            Reporter: Filip Maj
>            Assignee: Brent Lintner
>
> This came up when using ripple as a dependency to cordova.
> For more information see: https://issues.apache.org/jira/browse/CB-4058
> The important output bits are:
> > ripple-emulator@0.9.17 preinstall C:\Users\IBM_ADMIN\AppData\Roaming\npm\node_modules\cordova\node_modules\ripple-emulator
> > node thirdparty/ludicrous.js
> npm ERR! Error: spawn ENOENT
> npm ERR! at errnoException (child_process.js:980:11)
> npm ERR! at Process.ChildProcess._handle.onexit (child_process.js:771:34)
> npm ERR! If you need help, you may report this log at:
> npm ERR! <http://github.com/isaacs/npm/issues>
> npm ERR! or email it to:
> npm ERR! <np...@googlegroups.com>
> So it looks like the preinstall script is f'ed.
> For the record, NPM documentation suggests that preinstall scripts are an antipattern. Perhaps it would be worth investigating if that could be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira