Community
Participate
Working Groups
The EMF Model Validation framework should define an Ecore model of the meta-data required by the framework for the definition of constraints. This would capture, basically, the information defined for the default plugin.xml-based provider's extension-point schema. The advantages are: - removing the burden of large plugin.xml content from the Eclipse extension registry - modeling your data is always a good thing :-) The generated editor is easy to use, and potentially even a graphical editor (GMF-based) could be provided by the SDK - access to constraints defined in EMF resources, anywhere that EMF can find them: plug-in contents, HTTP on the web, repositories via CDO/JCRM, etc.
Cleaning up after the milestones were all deranged.
(In reply to comment #1) > Cleaning up after the milestones were all deranged. Hi, What about this Bug :D ??? I hope taht it will be soon fixed, cause it blocks Standalone Validation Bug ;) Thanks and best regards
Rudy, the fix is in HEAD. There will be a milestone release at sometime in the near future. Meanwhile you can try out the latest and greatest from Hudson.
Closing: as per the last comment, the fix had been commited at the time, and there has definitly been actual releases since then.