[jbosstools-issues] [JBoss JIRA] (JBIDE-19795) Bower support for JBDS 9

[Ilya Buziuk (JIRA)]

Ilya Buziuk created JBIDE-19795:
-----------------------------------

             Summary: Bower support for JBDS 9
                 Key: JBIDE-19795
                 URL: https://issues.jboss.org/browse/JBIDE-19795
             Project: Tools (JBoss Tools)
          Issue Type: Feature Request
    Affects Versions: 4.3.0.Alpha2
            Reporter: Ilya Buziuk
            Assignee: Ilya Buziuk
             Fix For: 4.3.x


Need to create initial [Bower|http://bower.io/] implementation for JBDS 9:
Bower tooling should initially support several bower API commands :


|Command||Description|
| *bower init* |creates a *bower.json* file|
|*bower install <package>*|installs packages to *bower_components* folder|
|*bower uninstall <package>*|uninstalls a package locally from your bower_components directory|
|*bower update* |updates installed packages to their newest version according to *bower.json*|

Basically, the main idea of the implementation is the following:
Eclipse plugin that will execute external commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*

*The main questions & proposals:*

1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
3. Implementation details:
- the way of detecting bower? Should user point to it's installation and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* ) 
- if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform" 




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)