[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [swtbot-dev] Moving build to Tycho
|
On 11/10/10 3:19 PM, Mickael Istria wrote:
This is a dependency of the junit4_x plugin. Some of the internal API
in junit 4.3 was declared an API somewhere in a later version.
JUnit 4.3 ships with eclipse 3.4. Junit 4.5 ships with eclipse 3.5.
Junit 4.8 ships with eclipse 3.6.
As far as compatibility is concerned, SWTBot needs to be compatible
with eclipse 3.4. There's more downloads for swtbot/3.4 than there is
for swtbot/3.6.
I totally agree with keeping compatibility. My aim at the moment is to
find an organization of bundles that would avoid the hack of MANIFEST
templates according to Eclipse/JUnit version in build.
What is the technical constraint? CQ #3000 allows SWTBot to be coupled
and shipped with JUnit 4.5. Let's take it from Orbit and put it on the
update site and write code against JUnit 4.5. Then we are sure that
anywhere SWTBot is installed, we have JUnit 4.5, and we don't have to
keep some deprecated code, we can remove bundles and then the
repository and the build are much easier to maintain.
Is there something wrong with this approach?
Ketan, what is your opinion on this suggestion?
If memory serves right. The JDT-JUnit bundles on some versions of
eclipse have an upper and a lower limit on the junit bundle. So
upgrading junit on certain versions of eclipse breaks jdt.
Shipping JUnit 4.3/4.5/4.8 is certainly doable, just need to keep this
dependency breakage in mind when doing any sort of osgi-foo :(
This is the primary reason I'd given up on split packages and different
bundles for different eclipse versions which pick up different manifests
and source dirs, and an ant file that gave me this control without
having to yakshave with osgi :(
--
Ketan
http://ketan.padegaonkar.name | http://eclipse.org/swtbot
