|Re: [wtp-dev] The Bower IDE contribution
On 03/24/2015 07:35 PM, Victor V. Rubezhny wrote:
Not in a 1st time, we'll work on another commit to integrate it as best in the build and delivery after code has moved to master. Let's do it step by step, 1st step is to put code into master.
I'd rather add an "Experiment/Incubation JSDT components" which would include such a Bower feature.Then next iteration would be to see if we can build it easily, include in the category.xml file as a separete entry, without modifying the "regular" JSDT feature so it wouldn't get in Mars. That would allow people who want to try it to get it from a p2 repository.I can create a category for Bower IDE, but again: what will go into this category in case we aren't adding the Bower plug-ins into the build? It looks for me that we have to add the bower-related plug-ins to pom.xml-s, to create a separated feature for bower and then include that feature into site/pom.xml and category.xml, but not to jsdt.feature/jsdt_sdk.feature.
About experimental stuff, there is also https://git.eclipse.org/r/#/c/44029/ which is waiting for review/merge. This is not meant to be part of Mars distribution neither, and as you can see, it is built and provided as a separate entry on the same update-site.
But I'm not sure if bower plug-ins will not became 'installable by default' in such case.There is no such concept as "installable by default". If no existing feature nor bundles links to Bower, nothing will install Bower magically.
Please put the Bower-related code to master ASAP if you want a good integration early. We don't want to have diverging branches, separate sites to test Bower, and distinct builds.
Back to the top