aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Farner <wfar...@apache.org>
Subject Re: [DISCUSS] Javascript dependencies location and bower
Date Thu, 27 Mar 2014 23:41:24 GMT
I'm open to either approach.  If we can install npm 'on-demand' like we do
with gradle and thrift, that probably makes sense.  I vote for the route
that distracts us less to getting to the first release.

-=Bill


On Thu, Mar 27, 2014 at 3:34 PM, Suman Karumuri <mansu@apache.org> wrote:

> What are the 3 locations you speak of? With the UI refactor work, most
> of the dependencies in src/ for scheduler will be removed. If you can
> file me a ticket with the issues you are facing, I can make sure that
> #1 happens.
>
> We should definitely revisit #2 once #1 is done.
>
> On Thu, Mar 27, 2014 at 1:39 PM, Jake Farrell <jfarrell@apache.org> wrote:
> > Currently the javascript dependencies we use within our source are
> > committed in three locations, this is the only bundled source type we
> > included within our source tree and currently we are required to maintain
> > each in the LICENSE file.
> >
> > To help simplify managing the LICENSE file I would like to propose
> >
> > 1. Move all javascript dependencies into 3rdparty/javascript/ to simplify
> > tracking of these within the LICENSE file. (I think this should be the
> > initial approach and look into #2 if we want to introduce npm as a build
> > dependency)
> >
> > 2. We remove all javascript dependencies from the source tree and use
> bower
> > to handle these dependencies. As part of the initial build process we
> would
> > then check for npm and install the javascript components.
> >
> > Thoughts?
> >
> > -Jake
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message