Hi Mickael e4 sounds works with me. The question is which of the current repos best fits your prototype.
Dani From: Mickael Istria <[email protected]> To: [email protected], [email protected] Date: 01.03.2016 14:59 Subject: [jdt-dev] Wish to contribute a draft of multiple classpath/scopes per JDT projects Sent by: [email protected] Hi all, I have started a *POC/draft* of a non-intrusive way to implement mulitple classpath per JDT projects (cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=105372 ). It's actually not about adding support for multiple classpath, but more about optionally adding some restrictions on classpath entries, and enabling a specific builder that reports error markers when using of a "restricted" class from the wrong scope. It doesn't require any change in JDT at the moment, and it's set up in a way that other projects like m2e or BuildShip could consume it, simply by setting the restrictions on the classpath entries and enabling the builder. I'd like to put my current progress somewhere useful, with a good infrastructure and good accessibility for our Eclipse contributor peers. I believe the org.eclipse.e4.ui repository could be a good place. Any objection against moving such code there? Cheers, -- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets_______________________________________________ jdt-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
