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?
--
Mickael Istria
R&D Engineer
This message and any attachment (the "message") is
intended solely for
the addressees and is confidential. If you receive this message by
mistake, please delete it and notify the sender immediately. Any use
not in accordance with its purpose, any out-spread or disclosure,
either as a whole or partially, is prohibited except with formal
approval. Internet cannot guarantee the integrity of this message,
therefore BonitaSoft will not be liable for the message if modified.
|
