uuhhhh, no :-) The startup.properties is completely created from the framework features.xml :-) The only startup.properties you find in an empty trunk are:
pieber@prime karaf]$ find -name startup.properties ./main/src/test/resources/test-karaf-home/etc/startup.properties ./itests/tests/src/test/resources/org/apache/karaf/testing/startup.properties ./instance/core/src/test/resources/etc/startup.properties @./main/src/test/resources/test-karaf-home/etc/startup.properties for unittests @./itests/tests/src/test/resources/org/apache/karaf/testing/startup.properties no idea why this one is here. I'll remove it; it does nothing in the karaf testframework we're using for our itests. @./instance/core/src/test/resources/etc/startup.properties for unittests So there is no need for manually editing any startup.property files (and even less for the itests). Kind regards, Andreas On Tue, May 8, 2012 at 10:29 AM, Christian Schneider <[email protected]> wrote: > Honestly I am not sure. I just see that we have a startup.properties in the > resources dir and learned that we have to keep it in sync with the > startup.properties from the > framework feature. > > So perhaps this is not necessary anymore? Can we delete this file then? > > Christian > > Am 08.05.2012 10:19, schrieb Andreas Pieber: > >> Hey, >> >> On Tue, May 8, 2012 at 9:01 AM, Christian Schneider >> <[email protected]> wrote: >>> >>> </SKIP> >>> - Makes our itests simpler as we do not need to sync the >>> startup.properties >>> anymore by hand >> >> Please explain that point in more detail. TBH I don't really get it >> how this will speed up the itests. Our itests (at least on the trunk) >> are based on the labs-paxexam-karaf bundles (well, the version moved >> to trunk) which is based on the assembly, not on anything build on the >> fly? *confused*. >> >> Kind regards, >> Andreas >> > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com >
