[ https://issues.apache.org/jira/browse/MYRIAD-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032573#comment-15032573 ]
Jim Klucar commented on MYRIAD-114: ----------------------------------- We went around a few times getting this right, and I just pulled and built inside vagrant from the latest master (commit c914c37334a6baf6aecd96710a0331c53227d614) and everything went fine. I read the document and perhaps you switched to the hduser before the build? I could see where the documentation isn't quite clear on that. Either way, if you could give some more details about what broke, and what your configuration is I can try and reproduce your problem. > Automatic dashboard building > ---------------------------- > > Key: MYRIAD-114 > URL: https://issues.apache.org/jira/browse/MYRIAD-114 > Project: Myriad > Issue Type: Bug > Reporter: Jim Klucar > Assignee: Jim Klucar > Fix For: Myriad 0.1.0 > > > Build the dashboard as part of the Myriad build process. This would require: > - [ ] npm install of dashboard dependencies > - [ ] removing files under webapp/public (could be part of gulp) > - [ ] running gulp script > Benefits: > Can remove myriad-scheduler/src/main/resources/webapp/public/* from git. This > is auto-generated each time gulp is run, so any diffs in this directory don't > mean anything and are just noise. > Drawbacks: > Users must have npm/node installed to build Myriad. (maybe we only build if > they have node installed?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)