Community
Participate
Working Groups
The contribution adds Bower support for JSDT and allows a user to manage their javascript projects by setting up the required packages, managing their versions and depencencies. How Bower works see: http://bower.io/
WARNING: this patchset contains 7347 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire
The Contribution Questionnaire was made and an IP Check for the contribution was passed according to: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=9173 - Bower support for JSDT
The initial contribution for review is pushed to Gerrit: https://git.eclipse.org/r/41693
WARNING: this patchset contains 7564 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire
WARNING: this patchset contains 7657 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire
The contribution is saved in a private branch named as 'bower' in JSDT repository: http://git.eclipse.org/c/jsdt/webtools.jsdt.git/log/?h=bower
As I argued on the wtp-dev mailing-list, I'd be in favour of merging it in master from now on, and just to mark it as incubation and to ship it separately from the main feature.
WARNING: this patchset contains 7914 new lines of code and may require a Contribution Questionnaire (CQ) if the author is not a committer on the project. Please see:https://wiki.eclipse.org/Project_Management_Infrastructure/Creating_A_Contribution_Questionnaire
As Bower IDE contribution is replaced by the native NPM/Bower support, closing it as a duplicate of Bug #481828 *** This bug has been marked as a duplicate of bug 481828 ***