Github user Leemoonsoo commented on the pull request:

    https://github.com/apache/incubator-zeppelin/pull/34#issuecomment-114658042
  
    Existing user who has build zeppelin will see this error without removing 
zeppelin-web/bower_components directory.
    ```
    [INFO] --- frontend-maven-plugin:0.0.23:bower (bower install) @ 
zeppelin-web ---
    [INFO] Running 'bower --allow-root install' in 
/Users/moon/Projects/zeppelin/zeppelin-web
    [INFO] bower angular-sanitize#1.2.28   cached 
git://github.com/angular/bower-angular-sanitize.git#1.2.28
    [INFO] bower angular-sanitize#1.2.28 validate 1.2.28 against 
git://github.com/angular/bower-angular-sanitize.git#1.2.28
    [INFO] bower angular-cookies#1.2.28    cached 
git://github.com/angular/bower-angular-cookies.git#1.2.28
    [INFO] bower angular-cookies#1.2.28  validate 1.2.28 against 
git://github.com/angular/bower-angular-cookies.git#1.2.28
    [INFO] bower angular-route#1.2.28      cached 
git://github.com/angular/bower-angular-route.git#1.2.28
    [INFO] bower angular-route#1.2.28    validate 1.2.28 against 
git://github.com/angular/bower-angular-route.git#1.2.28
    [INFO] bower angular-animate#1.2.28    cached 
git://github.com/angular/bower-angular-animate.git#1.2.28
    [INFO] bower angular-animate#1.2.28  validate 1.2.28 against 
git://github.com/angular/bower-angular-animate.git#1.2.28
    [INFO] bower ng-sortable#1.1.6         cached 
git://github.com/a5hik/ng-sortable.git#1.1.6
    [INFO] bower ng-sortable#1.1.6       validate 1.1.6 against 
git://github.com/a5hik/ng-sortable.git#1.1.6
    [INFO] bower angular-scenario#1.2.28   cached 
git://github.com/angular/bower-angular-scenario.git#1.2.28
    [INFO] bower angular-scenario#1.2.28 validate 1.2.28 against 
git://github.com/angular/bower-angular-scenario.git#1.2.28
    [INFO] bower angular-mocks#1.2.28      cached 
git://github.com/angular/bower-angular-mocks.git#1.2.28
    [INFO] bower angular-mocks#1.2.28    validate 1.2.28 against 
git://github.com/angular/bower-angular-mocks.git#1.2.28
    [INFO] bower angular-touch#1.2.28      cached 
git://github.com/angular/bower-angular-touch.git#1.2.28
    [INFO] bower angular-touch#1.2.28    validate 1.2.28 against 
git://github.com/angular/bower-angular-touch.git#1.2.28
    [INFO] bower angular#1.2.x             cached 
git://github.com/angular/bower-angular.git#1.2.28
    [INFO] bower angular#1.2.x           validate 1.2.28 against 
git://github.com/angular/bower-angular.git#1.2.x
    [INFO] bower angular#1.2.28            cached 
git://github.com/angular/bower-angular.git#1.2.28
    [INFO] bower angular#1.2.28          validate 1.2.28 against 
git://github.com/angular/bower-angular.git#1.2.28
    [INFO] bower angular#>=1               cached 
git://github.com/angular/bower-angular.git#1.4.1
    [INFO] bower angular#>=1             validate 1.4.1 against 
git://github.com/angular/bower-angular.git#>=1
    [INFO] bower angular#*                 cached 
git://github.com/angular/bower-angular.git#1.4.1
    [INFO] bower angular#*               validate 1.4.1 against 
git://github.com/angular/bower-angular.git#*
    [INFO] bower angular#>=1.0.6           cached 
git://github.com/angular/bower-angular.git#1.4.1
    [INFO] bower angular#>=1.0.6         validate 1.4.1 against 
git://github.com/angular/bower-angular.git#>=1.0.6
    [INFO] bower angular#~1.x              cached 
git://github.com/angular/bower-angular.git#1.4.1
    [INFO] bower angular#~1.x            validate 1.4.1 against 
git://github.com/angular/bower-angular.git#~1.x
    [INFO] bower angular#1.3.x             cached 
git://github.com/angular/bower-angular.git#1.3.16
    [INFO] bower angular#1.3.x           validate 1.3.16 against 
git://github.com/angular/bower-angular.git#1.3.x
    [ERROR] bower                        ECONFLICT Unable to find suitable 
version for angular
    ```
    
    Therefore, a lot of users will report building failure into the mailing 
list and JIRA.
    That's what we went through last time we changed angular version.
    Any idea of avoiding it?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to