Re: [Wonder-disc] JUnit/WOUnit in Jenkins

[Robin S. <rob...@cl...>]

Ahh I've found it

Now my classpath is fixed i no longer have to put junit.jar inside my ANT
build directory as it already exists in ERJars

Thanks Again

Robin

On 26 April 2012 16:35, Robin Smith <rob...@cl...> wrote:

> Hi Paul
>
> Thanks for pointing that out, now you have pointed me in the right
> direction i found some posts from yourself last year about this very same
> thing. Using wopath i get all of my frameworks etc which is great, all i
> need to do now is work out where i have created a hamcrest matcher linkage
> error but thanks for all your help.
>
>  <error message="loader constraint violation: loader (instance of java/net/URLClassLoader) previously initiated loading for a different type with name &quot;org/hamcrest/Matcher&quot;" type="java.lang.LinkageError">java.lang.LinkageError: loader constraint violation: loader (instance of java/net/URLClassLoader) previously initiated loading for a different type with name &quot;org/hamcrest/Matcher&quot;
>
> If your still interested my build xml is the default wonder one, so i
> added an extra target to run my tests
>
> <typedef name="wopath" classname="org.objectstyle.woproject.ant.WOPath" />
>
> <wopath id="classpath.test">
>
>  <frameworks root="ProjectLocal" embed="false" eclipse="true" />
>
>  <frameworks root="External" embed="false" eclipse="true" />
>
>  <frameworks root="Local" embed="false" eclipse="true" />
>
>  <frameworks root="User" embed="false" eclipse="true" />
>
>  <frameworks root="System" embed="false" eclipse="true" />
>
>  <frameworks root="Network" embed="false" eclipse="true" />
>
> </wopath>
>
> <property name="report.dir"  value="TestResults"/>
>
> <target name="test" depends="build">
>
>  <mkdir dir="${report.dir}"/>
>
>  <junit fork="no" printsummary="yes">
>
>  <classpath>
>
>   <pathelement location="bin" />
>
>   <fileset dir="Libraries">
>
>   <include name="*.jar" />
>
>   </fileset>
>
>   <fileset dir="${wo.extensions}">
>
>   <include name="*.jar" />
>
>   </fileset>
>
>  </classpath>
>
>  <classpath refid="classpath.test" />
>
>  <test name="test.MyTestSuite" todir="${report.dir}" haltonfailure="no"outfile
> ="result">
>
>   <formatter type="xml"/>
>
>  </test>
>
>  </junit>
>
> </target>
>
>
> On 26 April 2012 14:03, Paul Hoadley <pa...@lo...> wrote:
>
>> Hi Robin,
>>
>> On 26/04/2012, at 9:24 PM, Robin Smith wrote:
>>
>> > The exception depends on the test being run, for example if i touch
>> ERXStringUtilities in the method being tested then it complains that this
>> class cant be found.
>> >
>> > I think this may be where i'm going wrong on the Jenkins server the ANT
>> task does a wocompile which happily compiles my framework into my bin
>> directory. However the junit ANT task cant see my .classpath file and even
>> if it did it wouldnt understand where to look for the frameworks specified.
>> Do i actually have to manually recreate the classpath in my build.xml for
>> the junit task to use and make sure it matches the one in my .classpath
>> file.
>>
>> No, you don't have to do it manually, you can use a 'wopath' element to
>> create one for you.  Any chance you can post your build.xml to the list?
>>
>>
>> --
>> Paul.
>>
>> http://logicsquad.net/
>>
>>
>>
>
>
> --
> Robin Smith
> Software and Infrastructure Engineer  BEng (Hons) MBCS
>
>
>


-- 
Robin Smith
Software and Infrastructure Engineer  BEng (Hons) MBCS

-- 

------------------------------
Click Travel Ltd
Making a connection
http://www.clicktravel.com

Winner of "Best Business Travel Management Company" at the Business Travel 
Awards (2012 & 2009) and the Travel Trade Gazette Awards (2011)

Think: Do you really need to print this email?