Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[m2t-dev] [xpand] new plugin org.eclipse.xpand.support.cdt

I talked with Dennis via phone about the tasks that have to be done for integration of the CDT formatter. We agreed that the CDT plugin
- should be named org.eclipse.xpand.support.cdt
- should be integrated in the SDK
- must not cause an installation of CDT when the SDK is installed

First question is on naming. Is calling plugins like that org.eclipse.xpand.support.xyz OK? There could be potential several of them later, for each 3rd party product we aim to adapt.

Second question is planning. I'd like to introduce this plugin soon, at least to check in the sources and test the build against it. It is not required to integrate it in the M4 build, if any unexpected occurs or it could not be tested enough. In this case a precompiled version can be offered as separate download. Since we have more and more C++ projects I think this is a long-awaited feature. There are other C++ adapters based on 3rd party executables (e.g. Fornax Uncrustify Beautifier), but they are platform dependent and slow. CDT integration would be a real good new feature.

Please let me first know about the plugin structure, since then I could commit it initially.

Best,
~Karsten

Am 02.12.2009 um 20:25 schrieb Dennis Hübner:

Hi Karsten,
take a look at xtend.profiler plugin it's pretty new and mostly ok.
The feature definition? Well, maybe we can create a kind of aggregation feature "o.e.xpand.support" for optional bundles.
Have to investigate how to handle such a feature during p2 repo promotion/installation.

Regards,
Dennis.


Karsten Thoms schrieb:
Hi all,

I'd like to integrate the CDT formatter as Xpand postprocessor, as described in
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=197871.
Danial Weber added it as attachment, and I have adjusted it for M2T Xpand. I propose to create a new plugin "org.eclipse.xpand.adapter.cdt", which contains this PostProcessor.

What do I have to take into account to introduce the new plugin, e.g. build process, feature definition, legal issues, planning, documentation?

~Karsten



_______________________________________________
m2t-dev mailing list
m2t-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2t-dev

_______________________________________________
m2t-dev mailing list
m2t-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2t-dev


Back to the top