2 Replies Latest reply on Nov 2, 2009 12:22 AM by R Lenard

    jsfunitwar task too slow - what's wrong?

    R Lenard Newbie

      I have a war that with a normal task builds in a couple of seconds - but I pass it to JsfUnitWarTask and it's a dog [takes 2-20 minutes to build the same war, with just the libraries and unit tests added and web.xml changed].

      I have -

      <taskdef name="jsfunitwar" classname="org.jboss.jsfunit.ant.JSFUnitWarTask" classpathref="jsfunit.classpath" />


      And

      <jsfunitwar srcfile="${deploy.war}" destfile="${webtest.war}" autoaddjars="true">
       <!-- This is where you have compiled your jsfunit tests -->
       <classes dir="${compile-web-test.dir}"
       includes="**/*.class">
       </classes>
       <TestRunner />
      </jsfunitwar>
      

      Everything stops at the JSFUnitWar task and then after that really long time it spits out the sort of output I'd expect in 5 seconds (describing what it did).

      Any ideas?

        • 1. Re: jsfunitwar task too slow - what's wrong?
          Matt Wringe Master

          could you try it without the autoaddjars to see if that makes a difference?

          WIth autoadd jars it will try and find specific classes within all the jars on the classpath, if you have a lot of jars or some very large jars it may take a while to search through all of them. I suspect this is where its taking so long.
          You may need to add the jars yourself instead of using autoadd.

          • 2. Re: jsfunitwar task too slow - what's wrong?
            R Lenard Newbie

             

            "mwringe" wrote:
            could you try it without the autoaddjars to see if that makes a difference?


            No that doesn't make much of a difference - I added
            autoadd="false"
            to try it out.

            The disk doesn't seem to be utilized very heavily and the WAR is only 12MB in size [expanding it using JAR takes about 5 seconds and it's only slightly larger].

            It's a shame there's not more logging in the task - the vast majority of the time is before the output WAR is created.