10 Replies Latest reply on Feb 8, 2007 2:11 PM by theute

    Building from source behind firewall

    sasdav

      Boss Portal Version 2.4 sp1
      Did you get Portal from CVS? or download it? download
      JBoss AS Version 4.0.5
      Database Vendor and Version MySQL 5.0
      JDBC Connector and Version com.mysql.jdbc.Driver 5.0
      OS Platform Windows XP sp2
      JBOSS_HOME=D:\jboss-4.0.5.GA

      I'm trying to build and deploy from source and I'm having two problems. When I try to build datasource in the core directory I get the following:

      java.io.FileNotFoundException: D:\jboss-portal-2.4.1-src\core\..\thirdparty\libraries.ent (The system cannot find the file specified)

      There is in fact no thirdparty directory in d:\jboss-portal-2.4.1-src

      I created a portal-mysql-ds.xml file from what is shown in the docs and deployed it in JBOSS_HOME\server\default\deploy and it looks like JBoss is loading it all right so I move on. I change to the build directory and try build deploy and I get this:

      D:\jboss-portal-2.4.1-src\build>build deploy
      Executing D:\jboss-portal-2.4.1-src\build\..\tools\bin\ant.bat -logger org.apache.tools.ant.NoBannerLogger deploy
      Buildfile: build.xml

      createthirdparty:
      [mkdir] Created dir: D:\jboss-portal-2.4.1-src\thirdparty\antlr
      [get] Getting: http://repository.jboss.com/antlr/2.7.6.ga/component-info.xml
      [get] To: D:\jboss-portal-2.4.1-src\thirdparty\antlr\component-info.xml
      [get] Error getting http://repository.jboss.com/antlr/2.7.6.ga/component-info.xml to D:\jboss-portal-2.4.1-src\thirdpar
      ty\antlr\component-info.xml

      BUILD FAILED
      D:\jboss-portal-2.4.1-src\build\build.xml:356: The following error occurred while executing this line:
      D:\jboss-portal-2.4.1-src\build\build-thirdparty.xml:113: Unable to get remote file=D:\jboss-portal-2.4.1-src\thirdparty\antl
      r\component-info.xml url=http://repository.jboss.com/antlr/2.7.6.ga/component-info.xml

      I'm behind a firewall so I need to set the http.proxyHost and http.proxyPort before the build process will be able to get the file, but where do I do this? I've tried adding it to the command line and to the ARGS option in build.bat but neither helps.

      Any ideas?

        • 1. Re: Building from source behind firewall
          sasdav

          OK, I was able to get past that problem by adding the option to the build.xml but now I've got another problem.

          I'm getting about 100 errors like this:

          [execmodules] D:\jboss-portal-2.4.1-src\common\src\main\org\jboss\portal\common\command\ReflectedConfigurator.java:69: cannot
          resolve symbol
          [execmodules] symbol : class NoSuchAttachmentException
          [execmodules] location: class org.jboss.portal.common.command.ReflectedConfigurator
          [execmodules] public void setObject(AttributeType attribute, Object value) throws NoSuchAttachmentException
          [execmodules] ^

          I assume I'm missing a jar? Any idea which one?

          Thanks

          • 2. Re: Building from source behind firewall
            theute

            drop thirdparty directory, do a ant clean, and try again. maybe... I have no clue

            • 3. Re: Building from source behind firewall
              peterj

              The NoSuchAttachmentException class is located in ./common/src/main/org/jboss/portal/common/command, which should be part of the source you downloaded. Could you check that it is there?

              How are you doing the build? You should cd to the build directory and run the build script (build.bat or build.sh). It will build the individual components in the proper order.

              • 4. Re: Building from source behind firewall
                sasdav

                Peter,

                I'm doing exactly as you said, I change to the build directory and type build deploy.

                D:\jboss-portal-2.6.0-DR1-src\common\src\main\org\jboss\portal\common does not contain a command directory, so it looks like the download was incomplete.

                • 5. Re: Building from source behind firewall
                  peterj

                  Wait a second, earlier you indicated 2.4.1, now you identify 2.6. Which is it?

                  Looking at WinZip, it tells me that the 2.4.1 source tar.gz file contains 3796 files, 55,466KB.

                  • 6. Re: Building from source behind firewall
                    bvogt

                    Try setting:

                    <setproxy proxyhost="<your.proxy>" proxyport="<your.port>"/>
                    
                    at the top of .../build/buildthirdparty.xml
                    and a 'build deploy' afterwards

                    Burkhard

                    • 7. Re: Building from source behind firewall
                      sasdav

                      Yes, I tried 2.4.1 and 2.6 and had the exact same problem from the source download. I tried the cvs download since then and it compiled and deployed properly. But I'm getting NullPointerExceptions on the Theme. Still working on it.

                      • 8. Re: Building from source behind firewall
                        dleerob

                         

                        "bvogt" wrote:
                        Try setting:
                        <setproxy proxyhost="<your.proxy>" proxyport="<your.port>"/>
                        
                        at the top of .../build/buildthirdparty.xml
                        and a 'build deploy' afterwards

                        Burkhard


                        Thanks this sorted out my problem where my build couldnt connect. Now it can connect to the remote repository. It is taking forever though, how long does the initial build usually take?

                        • 9. Re: Building from source behind firewall
                          theute

                          It needs to get the 126MB of libraries so it mostly depends on your Internet connection

                          • 10. Re: Building from source behind firewall
                            theute

                            The 126MB rang a bell, that didn't sound right to me.

                            The thirdparty got on a diet, now you 'only' need to pull 42MB from the repository.

                            Sorry for the toubles.