[jbosstools-issues] [JBoss JIRA] (JBIDE-20592) Always mark 'bower_components' folder resource as 'Derived'

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-20592:
---------------------------------------------

[~vrubezhny] i do not think marking bower_components as derived automatically is the right solution here.

for target/* sure, but bower_components should be read by an efficient javascript parser so it seems like a 'bad' approach to default to make it derived.

> Always mark 'bower_components' folder resource as 'Derived'
> -----------------------------------------------------------
>
>                 Key: JBIDE-20592
>                 URL: https://issues.jboss.org/browse/JBIDE-20592
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: javascript-bower
>    Affects Versions: 4.3.0.Beta2
>            Reporter: Victor Rubezhny
>            Assignee: Ilya Buziuk
>            Priority: Critical
>             Fix For: 4.3.x
>
>
> Need to always mark the folder that is used by bower to download the dependencies specified in bower.json as 'Derived' in eclipse (call IResource.setDerived(true) on that folder).
> Note that the name of 'bower_components' folder may be regulated from .bowerrc file content, so the tooling should mark the correct folder as Derived according to the settings in .bowerrc file (if any).
> Derived resources means they were generated automatically, and user changes will be lost on next build. Also, the Derived-flag is to allow JSDT parser/validator to skip these resources if required.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)