rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jmeas Pls (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RAVE-1100) Introduce Bower
Date Tue, 08 Jul 2014 20:18:06 GMT

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

Jmeas Pls updated RAVE-1100:
----------------------------

    Issue Type: New Feature  (was: Improvement)

> Introduce Bower
> ---------------
>
>                 Key: RAVE-1100
>                 URL: https://issues.apache.org/jira/browse/RAVE-1100
>             Project: Rave
>          Issue Type: New Feature
>          Components: rave-portal
>            Reporter: Jmeas Pls
>
> The problem:
> https://github.com/apache/rave/blob/angular/rave-portal-resources/src/main/webapp/static/script/requireConfig.js#L22-L37
> Why is this a problem:
> By hardcoding versions we make it more difficult to work with versions of these libraries.
Bower, a client-side package manager, all but gives this to us for free.
> Using the ^ and ~ operators we get bug fixes/minor releases for free, and our dependency
tree, no matter how complex, is automatically solved for us. At the moment we're just hoping
that all of these versions play well together.
> Better yet, updating our dependencies with Bower is as simple as running `bower update`.
To seal the deal we get great integration with a handful of free services that make our lives
easier like Travis for CI and David to keep track of our dependencies.
> Last but not least, we can move dependencies like Bootstrap out of the repo.
> https://github.com/apache/rave/tree/angular/rave-portal-resources/src/main/webapp/static/css/bootstrap
> because they don't need to be in there.
> +1 to add Bower.



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

Mime
View raw message