Hi, Bertrand Delacretaz schrieb: > On Wed, Jan 21, 2009 at 3:22 PM, Felix Meschberger <[email protected]> wrote: >> ...ok, how about removing jcr install from the default build ? Like for >> example create a new inactive-by-default profile for jcrinstall ?... > > I'd be ok with that if we have a continuous integration setup where > those jcrinstall tests run regularly. Otherwise we tend to forget to > run those tests, until it's too late.
It depends on what you want to have: JCRInstall as part of the build or not. If we want to integrate JCRInstall into the main build, I suggest we also integrate the JCRInstall integration tests with the rest of the integration tests. Or the other way around: If I build the whole stuff, I am fine with building, what's there. If it includes JCRInstall, fine. If it doesn't fine, too. But if JCRInstall is included, it should be properly integrated like any other module we have. The problem basically is maintaining all these launchpad modules like app, webapp, jcrapp, testing and jcrinstall/testing tends to turn into a massive task. So reducing the number of these launchpad modules, would probable be something very helpful. It is much better now with the new structure, but it still is kind of a "mess" to set this up and we might want to come up with something better. How about this: We integrate the JCRInstall integration tests with the main integration tests by means of a build profile. You may then switch on or off this profile to run the integration tests with or without JCRInstall. WDYT ? Regards Felix > > I'm not sure about the status of that - we used to have a Continuum > setup IIRC, but I don't remember seeing messages from that lately. > > -Bertrand >
