Wish to contribute a draft of multiple classpath/scopes per JDT projects

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Wish to contribute a draft of multiple classpath/scopes per JDT projects

Mickael Istria-5
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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: Wish to contribute a draft of multiple classpath/scopes per JDT projects

Daniel Megert
Hi Mickael

e4 sounds works with me. The question is which of the current repos best fits your prototype.

Dani



From:        Mickael Istria <[hidden email]>
To:        [hidden email], [hidden email]
Date:        01.03.2016 14:59
Subject:        [jdt-dev] Wish to contribute a draft of multiple classpath/scopes per JDT projects
Sent by:        [hidden email]




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
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev


_______________________________________________
jdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-dev