On Mon, May 4, 2009 at 10:04 AM, Willem Jiang <[email protected]> wrote: > mvn clean install -Pci-build-profile (same with hudson) on the > camel-itest-osgi module. With this profile it works
Results : Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 > And you can run mvn clean install to see if there is any different result. And with regular mvn clean install I get Results : Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 So the problem could have been the repo being offline. > > BTW, it looks like ops4j.org is back, my local build is OK again. > > Willem > Claus Ibsen wrote: >> On Mon, May 4, 2009 at 7:37 AM, Willem Jiang <[email protected]> wrote: >>> Hi Claus >>> >>> Yes, I just found that (The tests were passed on my Windows box), >>> but now it looks like the http://repository.ops4j.org/maven2 is not >>> available, all tests are failed with this error. >>> ava.lang.RuntimeException: URL >>> [mvn:org.ops4j.pax.runner.profiles/log//1.3.0] could not be resolved. >>> at >>> org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:195) >>> at org.ops4j.net.URLUtils.prepareInputStream(URLUtils.java:134) >>> >>> Could you help me to run it on your mac? >> Yes I can run it on you demand. >> >> Is it just the camel-itest-osgi I need to run mvn clean install or do >> you need me to run some other mvn goal? >> >> >>> Willem >>> Claus Ibsen wrote: >>>> Hi Willem >>>> >>>> Its better now as the distribution can be build now. >>>> However the osgi tests fails in tear down >>>> >>>> http://hudson.zones.apache.org/hudson/job/Camel/org.apache.camel$camel-itest-osgi/135/testReport/org.apache.camel.itest.osgi/OSGiIntegrationSpringTest/testSendMessage__knopflerfish_/ >>>> >>>> >>>> >>>> Error Message >>>> >>>> BeanFactory not initialized or already closed - call 'refresh' before >>>> accessing beans via the ApplicationContext >>>> Stacktrace >>>> >>>> java.lang.IllegalStateException: BeanFactory not initialized or >>>> already closed - call 'refresh' before accessing beans via the >>>> ApplicationContext >>>> at >>>> org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:153) >>>> at >>>> org.springframework.context.support.AbstractApplicationContext.getLifecycleBeans(AbstractApplicationContext.java:1061) >>>> at >>>> org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:825) >>>> at >>>> org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.doClose(AbstractOsgiBundleApplicationContext.java:197) >>>> at >>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$501(AbstractDelegatedExecutionApplicationContext.java:69) >>>> at >>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$2.run(AbstractDelegatedExecutionApplicationContext.java:214) >>>> at >>>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) >>>> at >>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.normalClose(AbstractDelegatedExecutionApplicationContext.java:210) >>>> at >>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$NoDependenciesWaitRefreshExecutor.close(AbstractDelegatedExecutionApplicationContext.java:93) >>>> at >>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.doClose(AbstractDelegatedExecutionApplicationContext.java:236) >>>> at >>>> org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:794) >>>> at >>>> org.springframework.context.support.AbstractApplicationContext.destroy(AbstractApplicationContext.java:782) >>>> at >>>> org.apache.camel.itest.osgi.OSGiIntegrationSpringTestSupport.tearDown(OSGiIntegrationSpringTestSupport.java:58) >>>> >>>> >>>> >>>> On Sun, May 3, 2009 at 11:22 AM, Willem Jiang <[email protected]> >>>> wrote: >>>>> Hi Claus, >>>>> >>>>> I just did a quick fix for that, it is caused by the changing of the >>>>> Pax-Exam plugin 0.5.0. >>>>> My bad, I should test it before I upgraded the Pax-Exam. >>>>> >>>>> Willem >>>>> >>>>> >>>>> Claus Ibsen wrote: >>>>>> Hi >>>>>> >>>>>> Is it possible to get the OSGi integration test working on hudson again? >>>>>> >>>>>> This is the latest failure. See console output. >>>>>> http://hudson.zones.apache.org/hudson/job/Camel/134/console >>>>>> >>>>>> >>>>>> [INFO] Error for project: Camel :: OSGi Integration Tests (during >>>>>> install) >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] 'generate-paxexam-config' was specified in an execution, but >>>>>> not found in the plugin >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Trace >>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: >>>>>> 'generate-paxexam-config' was specified in an execution, but not found >>>>>> in the plugin >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle(DefaultLifecycleExecutor.java:1359) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1260) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) >>>>>> at >>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >>>>>> at >>>>>> org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) >>>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) >>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>>>>> at >>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>>>> at >>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>>>> at java.lang.reflect.Method.invoke(Method.java:585) >>>>>> at >>>>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) >>>>>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >>>>>> at hudson.maven.agent.Main.launch(Main.java:158) >>>>>> at hudson.maven.MavenBuilder.call(MavenBuilder.java:162) >>>>>> at >>>>>> hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:579) >>>>>> at >>>>>> hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:525) >>>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:69) >>>>>> at hudson.remoting.UserRequest.perform(UserRequest.java:23) >>>>>> at hudson.remoting.Request$2.run(Request.java:213) >>>>>> at >>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) >>>>>> at >>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269) >>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:123) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) >>>>>> at >>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) >>>>>> at java.lang.Thread.run(Thread.java:595) >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] BUILD ERRORS >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> [INFO] Total time: 68 minutes 31 seconds >>>>>> [INFO] Finished at: Sat May 02 06:29:08 PDT 2009 >>>>>> [INFO] Final Memory: 105M/215M >>>>>> [INFO] >>>>>> ------------------------------------------------------------------------ >>>>>> channel stopped >>>>>> [locks-and-latches] Releasing all the locks >>>>>> [locks-and-latches] All the locks released >>>>>> finished: FAILURE >>>>>> >>>>>> >>>> >>>> >>> >> >> >> > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
