Re: [e4-dev] [jdt-dev] Wish to contribute a draft of multiple classpath/

[Brian de Alwis <briandealwis@xxxxxxxxx>]

The e4 repositories does contain org.eclipse.jdt.core, and Jay had planned to fork org.eclipse.jdt.ui there too [1] to experiment with teasing apart JDT/UI into tooling support and UI components.  If pulling in code with history matters, forking org.eclipse.jdt.ui might be easiest?

Brian.

[1] https://dev.eclipse.org/mhonarc/lists/e4-dev/msg09377.html

On 1-Mar-2016, at 10:28 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On 03/01/2016 04:20 PM, Daniel Megert wrote:

Hi Mickael

Hi,

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

Between tools and ui (the ones that are configured with Jenkins/Gerrit/Sonar), I don't think one is much better than the other. I'd rather use the e4.ui which is more about general features for the IDE than the tools one, which is more targeting RCP developers.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev