One remark to the testing thing: the problem is that most of the packaging thing is not under the control of us but rather exam itself. Some of the most active exam maintainers are not listening on this list --> ops4j might be a good resource too.
Kind regards, Andreas On Tue, Apr 16, 2013 at 9:18 PM, Jean-Baptiste Onofré <[email protected]>wrote: > Hi, > > could you try to use src/main/resources/OSGI-INF/**blueprint ? > The path that you use doesn't look correct to me. > > Regards > JB > > > On 04/16/2013 06:30 PM, glsilverman wrote: > >> Well, if I put all my classes under src/test/java, and the blueprint file >> under src/test/resource/OSGI_INF/**blueprint, the test works. But this >> just >> means that I can't test the code in src/main/java, which is what is >> needed. >> >> Is there any way to accomplish this with the Karaf test container? >> >> >> >> -- >> View this message in context: http://karaf.922171.n3.nabble.** >> com/Help-testing-in-Karaf-2-3-**1-tp4028453p4028460.html<http://karaf.922171.n3.nabble.com/Help-testing-in-Karaf-2-3-1-tp4028453p4028460.html> >> Sent from the Karaf - Dev mailing list archive at Nabble.com. >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
