4 Replies Latest reply on Sep 13, 2005 11:45 AM by Dustin Hunter

    Compile Warnings

    Dustin Hunter Newbie

      When I compile using the latest JBoss I link against ${jboss.home}/lib and ${jboss.home}/server/all/lib and I get the warnings below. These jar files certainly do not exist in the directories, and I think they are being generated from the classpath's defined in some of the manifest files. I'm I just using jboss wrong or are these warnings expected?


      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\lib\log4j.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\lib\log4j-core.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\lib\log4j-core.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\lib\logkit-1.2.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\lib\avalon-framework-4.1.5.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\lib\concurrent-1.3.2.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\lib\antlr-2.7.2.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\deploy\ejb3.deployer\log4j.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\tools\jboss-4.0.3RC2\server\all\deploy\ejb3.deployer\log4j-core.jar": no such file or directory
      [javac] warning: [path] bad path element "C:\foo\lib\jaxws-2.0_20050825\lib\jsr173_1.0_api.jar": no such file or directory
      [javac] 10 warnings

        • 1. Re: Compile Warnings
          Darran Lofthouse Master

          Can you please show how you are attempting to copile your code. What command are you using? Are you using Ant? If you are using Ant what does the script look like?

          • 2. Re: Compile Warnings
            Dustin Hunter Newbie

            I'm sorry I assumed that others were having this problem as well, and the build code was not needed. I assumed this because the manifest in the lib/commons-logging.jar specifically reference "log4j.jar log4j-core.jar" on the classpath (which do not exist).

            Yes, we are using Ant. Code below. Thanks for looking.


            <path id="jboss.compile.classpath">
             <fileset dir="${jboss.dir}/lib">
             <include name="**/*.jar" />
             </fileset>
             <fileset dir="${jboss.dir}/server/all/lib">
             <include name="**/*.jar" />
             </fileset>
             <fileset dir="${jboss.dir}/server/all/deploy/ejb3.deployer">
             <include name="*.jar" />
             </fileset>
             <fileset dir="${jboss.dir}/server/all/deploy/jboss-aop-jdk50.deployer">
             <include name="*.jar" />
             </fileset>
            </path>
            
            <path id="compile.classpath">
             <path refid="jboss.compile.classpath"/>
             <path refid="testng.compile.classpath"/>
            </path>
            
            <javac destdir="${classes.dir}"
             source="${jcompiler.version}"
             target="${jcompiler.version}"
             deprecation="on"
             debug="${jcompiler.debug}"
             optimize="${jcompiler.optimize}">
            
             <classpath>
             <path refid="compile.classpath"/>
             </classpath>
             <src path="${src.dir}/java/"/>
             <compilerarg value="-Xlint" compiler="javac1.5"/>
            </javac>


            • 3. Re: Compile Warnings
              Darran Lofthouse Master

              What is your component that you are trying to compile? Generally the only jar you need to reference is jbossall-client.jar in the folder {jboss.home}/client

              • 4. Re: Compile Warnings
                Dustin Hunter Newbie

                We are building server components, beans, web services, etc. I thought the client libs were for client applications accessing jboss as opposed to running within (but I might very well be confused... still learning).

                It works if I use :

                <path id="jboss.compile.classpath">
                 <fileset dir="${jboss.dir}/client" includes="**/jbossall-client.jar" />
                 <!--fileset dir="${jboss.dir}/lib">
                 <include name="**/*.jar" />
                 </fileset>
                 <fileset dir="${jboss.dir}/server/all/lib">
                 <include name="**/*.jar" />
                 </fileset-->
                 <fileset dir="${jboss.dir}/server/all/deploy/ejb3.deployer">
                 <include name="*.jar" />
                 </fileset>
                 <fileset dir="${jboss.dir}/server/all/deploy/jboss-aop-jdk50.deployer">
                 <include name="*.jar" />
                 </fileset>
                 </path>


                Guess the jbossall-client does not contain the ejb3.0 stuff yet.

                Thanks