4 Replies Latest reply on Feb 16, 2003 12:26 PM by Juha Lindfors

    Build error on jboss-all

    Per Steffensen Newbie

      Hi

      I have just checked out jboss-all from CVS.

      I run build.bat to build. It does not complete successfully. I get some exception. I cant remember wich exception, but I can find out if any of you would like to know.

      But shouldnt I alway be able to just check out and build without any exceptions?

      Kind Regards Per Steffensen

        • 1. Re: Build error on jboss-all
          Juha Lindfors Master

          yes you should

          and it works

          • 2. Re: Build error on jboss-all
            Per Steffensen Newbie

            Thanks for the great answer ;-)

            It did NOT work!

            Now I checked out tagged version JBoss_3_0_3. When I try to build that I succeed. I guess it will be OK for me.

            • 3. Re: Build error on jboss-all
              Per Steffensen Newbie

              I WOULD like to be able to compile the current version of jboss-all.

              I have checked out jboss-all using:
              cvs checkout jboss-all

              I try to build using jboss-all/build/build.bat, and get the following output:
              Calling ..\tools\bin\ant.bat -logger org.apache.tools.ant.NoBannerLogger
              Buildfile: build.xml

              _buildmagic:init:
              Trying to override old definition of task property

              configure-project:
              [echo] groups: default
              [echo] modules: common,jmx,system,aop,cache,j2ee,naming,management,transaction,server,blocks,console,security,m
              ging,connector,varia,cluster,jetty,jboss.net,iiop

              _buildmagic:modules:most:

              ==============================================================
              ==
              == Executing 'most' in module 'common'...
              ==
              ==

              BUILD FAILED
              java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
              at xdoclet.util.LogUtil.getLog(LogUtil.java:26)
              at xdoclet.loader.ModuleFinder.findModules(ModuleFinder.java:114)
              at xdoclet.DocletTask.registerModules(DocletTask.java:533)
              at xdoclet.DocletTask.createDynamicElement(DocletTask.java:332)
              at org.apache.tools.ant.IntrospectionHelper.createElement(IntrospectionHelper.java:510)
              at org.apache.tools.ant.helper.ProjectHelperImpl$NestedElementHandler.init(ProjectHelperImpl.java:960)
              at org.apache.tools.ant.helper.ProjectHelperImpl$TaskHandler.startElement(ProjectHelperImpl.java:870)
              at org.xml.sax.helpers.XMLReaderAdapter.startElement(XMLReaderAdapter.java:333)
              at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1490)
              at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
              at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
              at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
              at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
              at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)
              at org.apache.crimson.parser.Parser2.externalParsedEntity(Parser2.java:2827)
              at org.apache.crimson.parser.Parser2.expandEntityInContent(Parser2.java:2545)
              at org.apache.crimson.parser.Parser2.maybeReferenceInContent(Parser2.java:2422)
              at org.apache.crimson.parser.Parser2.content(Parser2.java:1833)
              at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)
              at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
              at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
              at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
              at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
              at org.apache.tools.ant.helper.ProjectHelperImpl.parse(ProjectHelperImpl.java:155)
              at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:117)
              at org.jboss.tools.buildmagic.task.Ant.execute(Ant.java:246)
              at org.jboss.tools.buildmagic.task.module.ExecuteModules$1.run(ExecuteModules.java:329)
              at org.jboss.tools.buildmagic.task.module.ExecuteModules.executeModule(ExecuteModules.java:342)
              at org.jboss.tools.buildmagic.task.module.ExecuteModules.execute(ExecuteModules.java:217)
              at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
              at org.apache.tools.ant.Task.perform(Task.java:319)
              at org.apache.tools.ant.Target.execute(Target.java:309)
              at org.apache.tools.ant.Target.performTasks(Target.java:336)
              at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
              at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
              at org.apache.tools.ant.Main.runBuild(Main.java:610)
              at org.apache.tools.ant.Main.start(Main.java:196)
              at org.apache.tools.ant.Main.main(Main.java:235)

              It seems like LogFactory cant be found. The only place I can find LogFactory is in jar-files under thirdparty. So maby I should setup the building job so that it can see the jars in the thirdparty library.

              But how do I do that the easiest way?
              Why is it not setup for me already?
              Have I done something wrong?

              Thanx

              • 4. Re: Build error on jboss-all
                Juha Lindfors Master

                cvs co -rBranch_3_0 jboss-all