On Wed, Jul 2, 2014 at 12:16 PM, Chris Geer <[email protected]> wrote:
> On Wed, Jul 2, 2014 at 9:06 AM, Jmeas Apache <[email protected]> > wrote: > > > *We currently rely on Maven to accomplish these tasks for us.* > > > > Ah, well, in that case it's possible that we won't need Grunt. If Maven > > does all of that for us then we don't need to spend time solving an > > already-solved problem. > > > > My 2-cents...I'm all for using grunt. Maven is just plain slow for simple > things (non java things). It's good for builds, but it's slow. I'd also > like to see grunt used to do our less compiles at some point. > I am all for completely severing the UI from the java/server-side build process. I just didn't see the driver for it in the initial e-mail. > > > > > *I assume there is more to the desire to use Grunt. **Are you intending > on > > continuing* > > *the effort to pull the front-end code into its own, separate module?* > > > > This is certainly something we'd like to help with, especially if it aids > > us in the primary goal of getting the Angular branch to feature parity > with > > the master branch. > > > > Maybe we can hold off on introducing Grunt until we're more certain of > the > > benefits of moving away from Maven. > > > > > > On Wed, Jul 2, 2014 at 8:56 AM, Matt Franklin <[email protected]> > > wrote: > > > > > On Tue, Jul 1, 2014 at 4:04 PM, Jmeas Apache <[email protected]> > > > wrote: > > > > > > > Apache Rave is a non-trivial application to get up and running on a > new > > > > machine. Carl and I are thinking things could be greatly simplified > > with > > > > tools like Vagrant, Ansible and Grunt, so we'd like to hear the > > thoughts > > > of > > > > the Rave community on adding these tools. > > > > > > > > Our thoughts now are placing all of the Java & Java-related > > dependencies > > > to > > > > the Vagrant box. This will allow anyone to get the Java environment > by > > > > simply running `vagrant up`, instead of figuring out all of the > > > > dependencies on their local machine. > > > > > > > > > > We have had conversations around putting vagrant out there for people > to > > > get started. I think it is great that you took the initiative. The > only > > > question is where should it live in the code tree. > > > > > > > > > > > > > > A PR that introduces Vagrant (with Ansible for provisioning) can be > > seen > > > > over here: > > > > > > > > https://github.com/apache/rave/pull/2 > > > > > > > > and on Jira at: > > > > > > > > https://issues.apache.org/jira/browse/RAVE-1099 > > > > > > > > For development, we're thinking a typical Grunt workflow could be > > > > incorporated to make things really nice. The Tomcat server could be > > > booted > > > > up with a Grunt command, files could be linted and built, > > > > unit/integration/functional/whatever tests we want to add can be done > > > > automatically, and to top it off it can all be performed as you work > > with > > > > watch. > > > > > > > > > > We currently rely on Maven to accomplish these tasks for us. I assume > > > there is more to the desire to use Grunt. Are you intending on > > continuing > > > the effort to pull the front-end code into its own, separate module? > > > > > > > > > > > > > > We're working on an initial Grunt PR now, and should have it ready > > soon. > > > At > > > > first it will just do simple things, and can be iterated upon later. > > > > > > > > What do y'all think? > > > > > > > > > >
