Community
Participate
Working Groups
With the current API, it is not trivial to be able to create functional validation rules that are specific to a given context. (For instance, have a warning in a Catch block when empty or not a call to a logger when developing eclipse plugins). Here, on one side, we have AST, and on the other one, we have API for defining markers. The objective would be to combine the two to have an efficient framework to do so (as it is done for EMF validation, for instance). A first implementation of such framework has been designed & hosted on GitHub: https://github.com/awltech/eclipse-ast-validation/wiki/Quick-Start-Guide If you feel this is interesting, & if you need more information, feel free to comment the ticket, I'll be following it. Maxence Vanbésien Worldline mvaawl@gmail.com
Thanks for letting us know about your work. Before looking into your implementation here's a quick question: Have you considered an approach based on a CompilationParticipant instead of a separate builder? If you look at BuildContext & ReconcileContext there are methods for attaching CategorizedProblem's. Those may not be perfectly convenient for your purpose, I don't know. My feeling is that this approach could be more light-weight than the builder-based approach.
Hi Stephan, At first, thx for this quick feedback. To be honest with you, I didn't know about such API around Compilation Units. I've browsed quickly the javadoc of the classes you mentioned, and I agree on the fact that it looks more integrated than the usage of builders, even though I don't see yet how to condition the execution per project (currently, you can choose whether to enable the feature on a specific project, by applying the builder or not.) I prototype with the approach you propose & let you know. Thx again, Maxence mvaawl@gmail.com
Hello Stephan, I had a quick look at the proposal you made, and it appears that we can use such participants. I added the support of such in the implementation of the tool, but I kept the Builder-based implementation, for people who would like to execute the process in a more manual way. When you are able to look into the source code, don't hesitate to come back to me for any information. Thx for such judicious advice. ;) Maxence Vanbésien Worldline mvaawl@gmail.com
Sorry for double post, but I have one more general question. More than the tool proposed here, we have some other that we also would like to submit to the Eclipse community, at least for review. Is the creation of such tickets sufficient & relevant; or is there another dedicated process for submission of new projects ? Thx, Maxence Worldline mvaawl@gmail.com
