Le 08/11/2010 19:06, Ketan Padegaonkar a écrit :
Ok, let's debate. I think I'll split this thread in 2 parts: one in which one I'll ask for help while I progress on the build, and the other one in which one we could debate ;) 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? --
Mickael Istria
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. |
_______________________________________________ swtbot-dev mailing list swtbot-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/swtbot-dev