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

[Ilya Buziuk (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069069#comment-13069069 ] 

Ilya Buziuk commented on JBIDE-19795:
-------------------------------------

< it will make that JSDT will have 2 Bower supports
[~mickael_istria], AFAIK for now there is no decent bower support in JSDT due to dozens of performance issues, like:
- Installing the dependencies takes too long
- Install/Update command block the UI, no way to cancel the operation
- Update command doesn't follow the real bower's one
etc...
I don't really think that it's utterly important to the end user whether he gets bower from tools or jsdt.  
Proof me wrong, but as far as I'm concerned our initial aim is to get working bower support *fast* (JBDS 9 release) in our tools, and not to be coupled with JSDT releases schedule and other overheads. 

> Bower support
> -------------
>
>                 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
>              Labels: new_and_noteworthy
>             Fix For: 4.3.0.Final
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> 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 *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* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *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 dir 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)