Mickael,
One of the goals of WTP is to remain as backward compatible as possible. However, there have been several times in the past when a plugin wants to make use of a new Java or Platform method, which is a valid use case, and thus allowed. Or, expressed in a more concrete example:
For Neon, Dali moved all of their BREE levels to Java 8 and made use of the Java 8 constructs in their code. That's perfectly fine. But if someone were to press for all of WTP to move up to Java 8 just because the platform is at Java 8, that's not fine- we try to stay as backwards-compatible as possible.
Please let me know if you have any other questions/comments/concerns.
Sincerely,
- Carl Anderson
WTP Releng project lead
 Mickael Istria ---03/17/2016 01:07:11 PM---Hi all, I'd like to contribute the official integation of the smart importer
From: Mickael Istria <mistria@xxxxxxxxxx>
To: "wtp-dev@xxxxxxxxxxx" <wtp-dev@xxxxxxxxxxx>
Date: 03/17/2016 01:07 PM
Subject: [wtp-dev] Is it ok for next JSDT to depend on Platform 4.6?
Sent by: wtp-dev-bounces@xxxxxxxxxxx
Hi all,
I'd like to contribute the official integation of the smart importer into the main JSDT UI bundle, since the API is part of org.eclipse.ui.ide 3.12 that is part of Platform 4.6.
Is it OK to have such dependency to bleeding edge Platform in next JSDT, or do you want to keep backward compatibility so I should rather make it an optional bundle?
Thanks in advance,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
|
