[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Code formatting & clean-up standards.
|
Am 16.02.2011 00:14, schrieb Miles Parker:
I actually thought about building an EMF model and XPand editor for all of the project dependency stuff, Manifests, etc.. along with all of the other various bits and pieces we have to maintain. But that's only because I have unlimited time on my hands and some sort of a modeling sickness. :-P
I also thought about a model and a generator for these kinds of artifacts. That could not only solve the maintenance issues with hundreds of files with identical contents but also add benefits like rule based version range management for third party dependencies (including exemptions and their reasoning. why does the MANIFEST.MF format not allow comments?). On the other hand I'd lose the ability to modify the manifests with PDE's cool editor.
(I remember clearly the day when I discovered that one had to have a plugin project for one's feature (a feature plugin?)
You mean the branding plugin ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
that had to have all of the same kinds of descriptions, license txt, etc.. but naturally in a completely different format.)
On Feb 14, 2011, at 11:43 PM, Sven Efftinge wrote:
On Feb 14, 2011, at 9:43 PM, Miles Parker wrote:
It is a maintenance issue though. Actually it would be nice perhaps at a higher level -- but there is no such thing as a "product" or "release" project. I don't think there is a way to enforce .settings that would be applied to features. But given that there isn't a one-to-many relationship between plugins and features that probably wouldn't be a good idea anyway.
Have a look at Workspacemechanic (http://code.google.com/a/eclipselabs.org/p/workspacemechanic/)
I tried it and it felt pretty simple and straight forward.
In Xtext we currently have one project, from which we copy the settings to all other projects using a tiny script.
But as soon as we have time for that, I will definitely come back evaluating workspacemechanic.
Cheers,
Sven
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
