+1 for that. I was going to suggest this as well:). By the way, hopefully this will solve the hang problem reported in https://issues.apache.org/jira/browse/ARIES-560.
On Mon, Feb 7, 2011 at 11:05 AM, Jeremy Hughes <hugh...@apache.org> wrote: > +1 for that. > > > On 7 February 2011 10:54, zoe slattery <zoe.slatt...@gmail.com> wrote: > >> Toni - thanks for this. I've just raised >> https://issues.apache.org/jira/browse/ARIES-569 and, if no-one objects, >> I'll switch ARIES to depend on pax-exam 1.2.3. >> >> Matt - thanks for reporting this issue. >> >> Zoe >> >> In order to explain why version 1.2.3 is likely to fix your issue. >> The two items: >> - http://issues.ops4j.org/browse/PAXEXAM-191 >> - http://issues.ops4j.org/browse/PAXEXAM-174 >> where fixed in 1.2.3 and are somewhat related to instability on CI >> Servers. >> >> Those hangs are related to both: a race condition (PAXEXAM-174) and non >> optimal RMI registry management. >> This lead to not 100% reproducible hangs but are not (yet) reported with >> version 1.2.3 anymore. >> >> Toni >> >> On Fri, Feb 4, 2011 at 10:47 PM, zoe slattery <zoe.slatt...@gmail.com>wrote: >> >>> On 04/02/2011 19:13, Toni Menzel wrote: >>> >>> Hi, >>> >>> well not sure if i get the question right right.. >>> Pax Exam is a library like any other in your classpath. When using Maven, >>> then the pom is responsible for telling the version. >>> I don't know how Aries POM "Architecture" looks like, so different >>> projects have different opinions on how and where to manage the versions. >>> Reading from Zoes last comment, it looks like the versions are not >>> specified in the particular project pom (integration test project). That >>> means they are inherited from the parent. >>> >>> Correct - we default to pax-exam 1.2.1 in the parent pom, so it can be >>> quite hard if your aren't used to Maven to figure out how to specify the >>> version in the samples. The long term answer is that we need to set the >>> default for pax exam to be 1.2.3 in the Aries parent, but this won't be >>> avaliable to people who want to use released code until we next next >>> release, so using a work around to override the version in the sample >>> blog-itests pom is a good plan - I just wasn't sure if that was the right >>> way to go earlier on. >>> >>> I would like to understand why switching the pax-exam version got rid of >>> the hang, was it a known issue in pax-exam? I've never seen it hang using >>> 1.2.1. >>> >>> Zoe >>> >>> >>> >>> So either change the parent (and build that too!) or add explicit >>> versions (=overwrite the inherited one). >>> This is a quick solution that is not bad at all. But its not following >>> the existing Aries POM architecture. For that you need to find the version >>> specified in one of the inherited super poms. >>> >>> Is is this what your problem is about ? >>> >>> Toni >>> >>> >>> On Fri, Feb 4, 2011 at 7:33 PM, zoe slattery <zoe.slatt...@gmail.com>wrote: >>> >>>> That is a good question. >>>> >>>> I just edited blog/blog-itests/pom.xml and inserted >>>> <version>1.2.3</version> after _every_ pax-exam artifact. This seems to do >>>> it. >>>> >>>> Here is a subsection of the pom: >>>> >>>> <dependency> >>>> <groupId>org.ops4j.pax.exam</groupId> >>>> <artifactId>pax-exam-junit-extender-impl</artifactId> >>>> <version>1.2.3</version> >>>> <scope>test</scope> >>>> </dependency> >>>> >>>> Toni may be able to provide a better answer, but I think this works. >>>> Zoe >>>> >>>> >>>> Hi Emily, >>>> I'm running the Itests module* "Apache Aries Blog sample iTests 0.3".* >>>> >>>> How do I specify from with in the test class what version of PAX EXAM to >>>> use? >>>> >>>> @RunWith(JUnit4TestRunner.class) >>>> public class JpaBlogSampleWithEbaTest extends AbstractIntegrationTest { >>>> ..... >>>> } >>>> >>>> This is the PAX/JUnit 4 test class. >>>> >>>> How do I specify from within this class the PAX EXAM version I want to >>>> use? >>>> >>>> Thanks >>>> Matt >>>> >>>> >>>> >>>> *Emily Jiang <emijia...@googlemail.com> <emijia...@googlemail.com>* >>>> >>>> 02/03/2011 04:26 PM >>>> Please respond to >>>> user@aries.apache.org >>>> >>>> To >>>> user@aries.apache.org >>>> cc >>>> >>>> Subject >>>> Re: Blog Sample 0.3.0 Itests hanging >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Thu, Feb 3, 2011 at 9:34 PM, Valentin Mahrwald <* >>>> vmahrw...@googlemail.com* <vmahrw...@googlemail.com>> wrote: >>>> Hi Matt, >>>> >>>> if I understand correctly this is not an intermittent problem. Is there >>>> a test log (in target/surefire-reports) or a thread dump you could get from >>>> your system and attach to say a JIRA? >>>> >>>> This would really help since I have not seen a problem like this on my >>>> system before :( >>>> >>>> Regards, >>>> >>>> Valentin >>>> >>>> On 3 Feb 2011, at 20:54, >>>> *matt_madha...@bcbsil.com*<matt_madha...@bcbsil.com>wrote: >>>> >>>> >>>> Hello, >>>> I just checked out the Aries Sample projects from SVN today. For the >>>> sample Blog I ran maven install. The tests just hang and nothing happens. I >>>> had the same issue with 0.2.0 Incubating as well. >>>> >>>> Can some one please take a look at this please? Been stuck on this for a >>>> while! (integration testing is core piece that I need to demonstrate before >>>> my client can adopt the OSGi technology!) >>>> >>>> The following is the tail end of the output: >>>> ---------------------------------------- >>>> [INFO] Copying 3 resources >>>> [INFO] >>>> [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ * >>>> org.apache.ar* <http://org.apache.ar/> >>>> ies.samples.blog.itests --- >>>> [INFO] No sources to compile >>>> [INFO] >>>> [INFO] --- maven-resources-plugin:2.4:testResources >>>> (default-testResources) @ or >>>> g.apache.aries.samples.blog.itests --- >>>> [INFO] Using 'UTF-8' encoding to copy filtered resources. >>>> [INFO] skip non existing resourceDirectory >>>> C:\working\aries\samples-0.3\blog\blo >>>> g-itests\src\test\resources >>>> [INFO] skip non existing resourceDirectory >>>> C:\working\aries\samples-0.3\blog\blo >>>> g-itests\src\test\filtered-resources >>>> [INFO] Copying 3 resources >>>> [INFO] >>>> [INFO] --- maven-compiler-plugin:2.0.2:testCompile (default-testCompile) >>>> @ org.a >>>> pache.aries.samples.blog.itests --- >>>> [INFO] Compiling 4 source files to >>>> C:\working\aries\samples-0.3\blog\blog-itests >>>> \target\test-classes >>>> [INFO] >>>> [INFO] --- maven-surefire-plugin:2.4.3:test (default-test) @ * >>>> org.apache.aries.sa* <http://org.apache.aries.sa/> >>>> mples.blog.itests --- >>>> [INFO] Surefire report directory: >>>> C:\working\aries\samples-0.3\blog\blog-itests\ >>>> target\surefire-reports >>>> >>>> ------------------------------------------------------- >>>> T E S T S >>>> ------------------------------------------------------- >>>> Running org.apache.aries.samples.blog.itests.JpaBlogSampleWithEbaTest >>>> >>>> >>>> >>>> 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. >>>> >>>> >>>> Hi Matt, >>>> >>>> I recall you reported the hang problem a few days. Are you still >>>> experiencing the hang problem even though you use pax exam 1.2.3 suggested >>>> by Toni? >>>> >>>> -- >>>> Thanks >>>> Emily >>>> ================= >>>> Emily Jiang* >>>> **eji...@apache.org* <eji...@apache.org> >>>> >>>> >>>> >>> >>> >>> -- >>> *Toni Menzel - http://www.okidokiteam.com* >>> >>> >>> >> >> >> -- >> *Toni Menzel - http://www.okidokiteam.com* >> >> >> > -- Thanks Emily ================= Emily Jiang eji...@apache.org
