Hi, Am Donnerstag, den 13.03.2008, 11:43 +0100 schrieb Bertrand Delacretaz: > On Wed, Mar 12, 2008 at 10:55 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > > ...I only see a solution by splitting > > the web app (to be compiled for pre-1.5) and the integration tests (to > > be compiled for 1.5).... > > I'd be ok with that, provided that doesn't make running or developing > the tests harder. > > A related thing that has been on my mind for a while is to allow OSGi > bundles to contain automated tests that could be executed via the > Sling console or via a Sling test harness. That's probably not too > hard to do, and that would allow the integration tests to be simply > provided as a bundle, but I don't have cycles ATM to work on that.
That would be an interesting approache to splitting the integration tests and the web app: the tests are deployed as just another bundle and then there would be some runtime controller to start them ... > > > ... OTOH it is also up to discussion, whether we implement SLING-190 at > > all ?... > > I think it's good to have such startup environment checks, if that's > not too "expensive". The most expensive part was reverting the generics stuff we used in the app and webapp to plain old Java. That's it. The rest is not concerned, and this is actually quite nice ;-) Regards Felix > > -Bertrand
