Hi Zoe,
Thanks for the reply! Its not that the some of the tests take long time to 
run. I left the tests running for over night! :) It was still haninging.

You are right on the applications though! I can build and launch the 
application ignoring the tests.

I'm in the process of creating standards for the OSGi bases integration 
testing for my current clinet. This seems to be a good reference point 
(Blog sample). Any help will be appreciated.

Thanks
Matt





zoe slattery <zoe.slatt...@gmail.com> 
01/27/2011 11:27 AM
Please respond to
user@aries.apache.org


To
user@aries.apache.org
cc

Subject
Re: Aries Sample Blog Example - ITests not working






On 26/01/2011 23:27, matt_madha...@bcbsil.com wrote: 

Hello, 
When I run the Integerations tests for the Blog example it shows the 
fowwing example and the test just hangs? I see the following line: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.4.3:test (default-test) @ 
org.apache.aries.sa 
mples.blog.itests --- 
[INFO] Surefire report directory: 
C:\working\aries\samples-0.2-incubating\blog\b 
log-itests\target\surefire-reports 

------------------------------------------------------- 
 T E S T S 
------------------------------------------------------- 
Running org.apache.aries.samples.blog.itests.JpaBlogSampleWithEbaTest 



And nothing happens after this? Any ideas? 

Hi Matt - sorry for a bit of a slow response. I'm afraid it's because I 
have no idea why this wouldn't work. Some of the tests are a bit slow, so 
depending on what you are running on you may need to give it a while to 
run.

If you build without running the tests (use something like maven
.test.skip=true, I think) does the blog sample build and can you run it 
OK?

Zoe


Thanks 
Matt 


HCSC Company Disclaimer

The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of
the addressee.  Unauthorized use, disclosure, distribution or copying is
strictly prohibited and may be unlawful.  If you have received this
communication in error, please notify the sender immediately at (312)
653-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in
Oklahoma; or (972)766-6900 in Texas. 

Reply via email to