You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Jmeas Pls (JIRA)" <ji...@apache.org> on 2014/07/08 22:18:06 UTC

[jira] [Updated] (RAVE-1101) Introduce Grunt

     [ https://issues.apache.org/jira/browse/RAVE-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jmeas Pls updated RAVE-1101:
----------------------------

    Issue Type: Improvement  (was: Bug)

> Introduce Grunt
> ---------------
>
>                 Key: RAVE-1101
>                 URL: https://issues.apache.org/jira/browse/RAVE-1101
>             Project: Rave
>          Issue Type: Improvement
>          Components: build & development, rave-portal
>            Reporter: Jmeas Pls
>
> Grunt can do lots of things for us, and I think we would benefit quite a bit if we were to switch to it.
> A handful of things it could do for us:
> 1. Providing a layer of abstraction between the user's machine and the Vagrant box. This would let us run Grunt commands to perform actions on the Vagrantbox, like running cargo to get the webserver running.
> 2. If separating the Java backend from the frontend is a goal we're pursuing, then Grunt is a great first step toward reaching that goal. From what I've gathered Maven is currently used to build the files, set up a watch environment, and run tests. Grunt can do this for us without a dependency on Java.
> 3. I've been told Maven is slow at the build process. We might see a speed bump by switching to Grunt.
> [~mfranklin] and [~geerzo] agreed that this is an idea they'd like to see implemented.
> //cc [~carldanley]



--
This message was sent by Atlassian JIRA
(v6.2#6252)