You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Suman Karumuri (JIRA)" <ji...@apache.org> on 2014/05/23 01:39:01 UTC

[jira] [Created] (AURORA-468) Better story for adding client libraries

Suman Karumuri created AURORA-468:
-------------------------------------

             Summary: Better story for adding client libraries
                 Key: AURORA-468
                 URL: https://issues.apache.org/jira/browse/AURORA-468
             Project: Aurora
          Issue Type: Story
          Components: UI
            Reporter: Suman Karumuri


Currently, we manage all the client side libraries with bower. While it keeps the dependencies sane, it adds entire repositories to our repo which is annoying to maintain and a pain to review[1]. We can use something like bower-installer[2], so that we only download the files we want from the bower repo instead of downloading everything. 

However, we are still checking in 3rd party libs in to repo.  We can solve this if we can take a build time dependency on bower, but that entails taking a build time dependency on node.js. 

An ideal solution would involve, a solution that will allow us to manage client libraries without checking in any JS lib source code into our repo using the existing build infrastructure.

[1] https://reviews.apache.org/r/21790/
[2] https://github.com/blittle/bower-installer



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