3 Replies Latest reply on Oct 7, 2005 5:13 AM by thomas.diesler

    Restructure of test build script

    thomas.diesler

      Hi Folks,

      I restructured webserservice/test/build.xml

      $ ant tests

      Still runs all tests with wstools artifact generation turned off - so no change

      $ ant tests-jaxrpc

      Runs all tests except the tools tests. By default wstools artifact generation is turned off.

      To run with wstool artifacts use: ant -Dwstools=true tests-jaxrpc

      3) $ ant tests-tools

      Runs the tools tests only

      The upcomming wstools release will be able to generate *.wsdl, *.xsd, jaxrpc-mapping.xml, webservices.xml
      These artifacts are currently generated by wscompile or hand coded. They live in ${resources.dir}

      As part of the build process we copy all resources to ${build.resources.dir} and jar them from there.
      There is a new target "wstools-resources", which is only enabled if the -Dwstools=true property is set.
      It clears the wscompile artifacts from ${build.resources.dir}, generates them using wstools (TBD),
      and finally copies artifacts that cannot (yet) be generated from ${resources.dir}/tools-overrides.
      The resources in ${resources.dir}/tools-overrides are an exact copy of what we have in ${resources.dir}

      The goal is to have less and less files in ${resources.dir}/tools-overrides. Once we are comfortable with what
      wstools generates we should remove all generatable artifacts from ${resources.dir} and only have a few edge cases
      covered in ${resources.dir}/tools-overrides

      Anil, please have a look at target wstools-resources. Does this approach make sense to you?

        • 1. Re: Restructure of test build script
          anil.saldhana

          As it stands today:

          The optional "wstools-resources" basically calls another ant script where the wstools resources are generated.

          =============================================


          <!-- Generate the tools artifacts -->












          =============================================

          Note that build-jars.xml still continues to package the ws deployment archives.

          • 2. Re: Restructure of test build script
            anil.saldhana

            As it stands today:

            The optional "wstools-resources" basically calls another ant script where the wstools resources are generated.

            <target name="wstools-resources" if="wstools"
             description="Generate deployment resources.">
            
             <!-- Generate the tools artifacts -->
             <ant antfile="build-tools-artifacts.xml" target="build-tools-artifacts"/>
             <copy todir="${build.resources.dir}">
             <fileset dir="${resources.dir}">
             <include name="**/*web.xml"/>
             <include name="**/jboss*.xml"/>
             <include name="**/ejb*.xml"/>
             <include name="**/application*.xml"/>
             <exclude name="**/*Config.xml"/>
             <exclude name="**/config.xml"/>
             </fileset>
             </copy>
             </target>
            

            Note that build-jars.xml still continues to package the ws deployment archives.

            • 3. Re: Restructure of test build script
              thomas.diesler

              Yes, this is what we need. Please be explicit where you can, avoiding extensive use of wildcards.