Hi Stephane!
We've looked at the code you provided at
https://github.com/sbegaudeau/webtools.jsdt
We'd like you to contribute your projects into JSDT on one by one
basic. To do that we need to split the code into a number of
projects that don't depend on each other.
For example, o.e.w.jsdt.bower.core has a dependency to
o.e.w.jsdt.nodejs.core because of using Semantic Versioning
classes that are defined in nodejs.core. If it's possible to
replace those SemVer classes with the ones defined in jsemver
project (See:
https://github.com/zafarkhaja/jsemver) - we would
never need to have that dependency from bower to nodejs.
[Note: JSemVer is not in JSDT Target Platform at the moment, but
probably we're able to force the inclusion of it into Orbit
bundle.]
We've found some external libraries that are used in your project
that aren't included into JSDT or WTP Target Platform, as such we
have to remove/replace them with some existing other libraries or
force the adding of them into the TP for JSDT or WTP:
- org.eclipse.xtend.lib
- org.eclipse.xtext.xbase.lib
- org.eclipse.jgit
We're going to investigate on possibility to include these
libraries into the JSDT or WTP Target platform.
Once the project is split into the independent pieces and the
listed required libraries are added into the JSDT/WTP TP you can
initiate contributing your projects to JSDT one by one. I think
this way is much simpler than trying to contribute it by one
piece.
Thanks,
Victor Rubezhny
On 10/31/2014 01:14 PM, Stéphane Bégaudeau wrote:
Hi,
I will start by presenting myself, my name is Stéphane Bégaudeau,
I am working for Obeo and I am a contributor or leader in some
projects of the Eclipse Foundation. I may have seen some of you
during EclipseCon Europe 2014 this week while I was presenting a
talk on web application development.
I would like to contribute to the Eclipse JSDT project to improve
the tooling for _javascript_ and front-end development. I am
currently working on the integration of tools like npm, bower,
node, gulp and grunt in the Eclipse IDE. You can find my code on Github,
it’s still a work in progress with some experiments inside. When
my code will be more stable and tested, I will try to contribute
it using Gerrit.
In the end, this tooling would include:
- a launch configuration for node.js
applications
- a basic Java implementation of bower built on
top of JGit and a Java implementation of
node.js
semantic versioning engine
- actions dedicated to bower, npm, grunt and gulp
- dedicated views to manage the dependencies of a node
application or web application project (bower and nom
dependencies)
- some preferences pages
- some wizards for _javascript_ and web applications (in order
to make users follow some of the best practices available)
- a builder that can be plugged to gulp or grunt
I have attached a couple screenshots in order to show you
what I had in mind or what I have already done.
Regards,
Stephane Bégaudeau, Obeo
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev