Hi, Thanks for nagging; it's very profitable for SimRel quality!
Let's split the discussion into several topics: 1. LSP4E contribution is incorrect: this is covered by https://bugs.eclipse.org/bugs/show_bug.cgi?id=557998 (and should be fixed later today) 2. Why an erroneous contribution doesn't cause a validation failure on CI? It was my expectation that the aggregator would let those errors get in; I was wrong. I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=558013 3. Forcing usage of the editor: although it has some nice features, it's not really more convenient than a text editor, so I don't think enforcing is ever fully possible, neither technically nor by human influence/education. In most current workflows, the review/CI is expected to be the quality gatekeeper, not the tool. So such valuable features of the editors should be made also profitable by the build validation step to get the best of both worlds. Cheers,
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
