5 Replies Latest reply on May 29, 2007 10:16 AM by Kevin Conner

    Problems building the product

    Andre Fernando Salvati Novice

      Hi,

      thanks for ESB team in promptly answer with corrections. :)

      I've donwloaded the trunck version and had some problems.

      Could you correct \product\build\jbossesb\samples\quickstarts\conf\base-build.xml?

      Change:

       <dirname property="quickstarts.dir" file="${pwd}"/>
       <dirname property="product.dir" file="${quickstarts.dir}/.."/>
      


       <dirname property="quickstarts.dir" file="${pwd}/.."/>
       <dirname property="product.dir" file="${quickstarts.dir}/../.."/>
      






        • 1. Re: Problems building the product
          Tom Fennelly Master

          The modification's you're looking for do look to be correct, but would you mind clarifying how these are causing issues for you. These settings look to be wrong for over a month now (since before MR2 went out).

          Also remember that this build script gets imported into the build scripts for the individual quickstarts. Even with that accounted for, they still look to be wrong :-)

          • 2. Re: Problems building the product
            Andre Fernando Salvati Novice

             

            "tfennelly" wrote:
            The modification's you're looking for do look to be correct, but would you mind clarifying how these are causing issues for you. These settings look to be wrong for over a month now (since before MR2 went out).

            Also remember that this build script gets imported into the build scripts for the individual quickstarts. Even with that accounted for, they still look to be wrong :-)


            Seems there are some differences between base-build.xml from MR2 in and from the trunck.

            When I run the trnck's version Ant is complaning on this validation:

            <condition property="esb.product.lib.dir.src.or.ga"
             value="${product.dir}/build/jbossesb/lib" else="${product.dir}/lib/ext">
             <available file="${product.dir}/build/jbossesb/lib/jbossesb-rosetta.jar"/>
             </condition>
            


            • 3. Re: Problems building the product
              Daniel Bevenius Master

              Hi,

              just wanted to point out that the properties are set with dirname and are not normal properties.
              So:

              <dirname property="quickstarts.dir" file="${pwd}/.."/>
              <dirname property="product.dir" file="${quickstarts.dir}/../.."/>
              

              Would actually cause ${product.dir} to point to the directory above the "product" dir.

              But there is obviously something wrong here as it is not working for you. Could you post the error or output of the ant target you are running?


              Thanks,

              Daniel

              • 4. Re: Problems building the product
                Andre Fernando Salvati Novice

                Hi Beve,

                this is the error. It happens when I try to deploy HelloWorld example.

                C:\ESB-trunck\product\build\jbossesb\samples\quickstarts\helloworld>ant deploy
                Buildfile: build.xml
                
                BUILD FAILED
                C:\ESB-trunck\product\build\jbossesb\samples\quickstarts\helloworld\build.xml:9:
                 The following error occurred while executing this line:
                C:\ESB-trunck\product\build\jbossesb\samples\quickstarts\conf\base-build.xml:77:
                 JBossESB must be built. Please run 'ant' in C:\ESB-trunck\product\build\jbossesb
                
                Total time: 0 seconds
                


                There's no build.xml at C:\ESB-trunck\product\build\jbossesb.

                Thanks.

                • 5. Re: Problems building the product
                  Kevin Conner Master

                  Daniel/Andre.

                  I am looking at these issues at the moment, going through all the combinations of deployment environments.

                  I have a restructured base-build.xml which should fix this and will check it in once I have verified the other QSes in these environments.

                  Kev