You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Sung Kim <hu...@hotmail.com> on 2003/01/17 00:02:54 UTC

Could you specify more detail error message for dependancy?

detect.fail:

BUILD FAILED

.........build.xml:334: Failed dependancy
  One or more required libraries could not be found.
  Please check your build.propertes file.

How do I know which library is not found? Could you make it to give us more 
specific error message?

--
Sung Kim, UCSC


_________________________________________________________________
MSN 8: advanced junk mail protection and 2 months FREE*. 
http://join.msn.com/?page=features/junkmail


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Could you specify more detail error message for dependancy?

Posted by Christopher Lenz <cm...@gmx.de>.
Sung Kim wrote:
> detect.fail:
> 
> BUILD FAILED
> 
> .........build.xml:334: Failed dependancy
>  One or more required libraries could not be found.
>  Please check your build.propertes file.
> 
> How do I know which library is not found? Could you make it to give us 
> more specific error message?

Run Ant with the '-verbose' option, as in

ant -verbose detect

Also, there's a lot of output before the failure message, which should 
already contain a hint on which library is missing.

-- 
Christopher Lenz
/=/ cmlenz at gmx.de


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Could you specify more detail error message for dependancy?

Posted by Andreas Probst <an...@gmx.net>.
On 16 Jan 2003 at 23:02, Sung Kim wrote:

> detect.fail:
> 
> BUILD FAILED
> 
> .........build.xml:334: Failed dependancy
>   One or more required libraries could not be found.
>   Please check your build.propertes file.
> 
> How do I know which library is not found? Could you make it to
> give us more specific error message?

type ant detect

See the following example. Every library which isn't true could 
not be found.

     [echo] Required libraries:
     [echo]   Servlet API 2.3               ${servlet23.present}
     [echo]   JAXP (1.0 or later)           true
     [echo]   XML DOM Level 2 API           true
     [echo]   XML SAX 2 API                 true
     [echo]   Java Transaction API          ${jta.present}
     [echo]   JDOM (current dev version)    true
     [echo]   Commons-Httpclient            true
     [echo]   Commons-Logging               true
     [echo]   ANTLR                         true
     [echo]   ANTLR Tools                   true

     [echo] Optional libraries:
     [echo]   JAXP 1.1                      true
     [echo]   JDBC 2.0 optional package     true
     [echo]   JMX                           ${jmx.present}
     [echo]   Commons-Modeler               true
     [echo]   Ant                           true
     [echo]   Ant <style>-task              true
     [echo]   JUnit                         true
     [echo]   Log4J                         ${log4j.present}
     [echo]   JNDI                          true
     [echo]   Struts (1.0 or later)         ${struts.present}
     [echo]   JSTL 1.0                      ${jstl.present}
     [echo]   Standard Taglib (1.0 or later)${taglibs-standard.present}
     [echo]   Tomcat (4.1 or later)         ${catalina.present}
     [echo]   Tomcat naming.jar             ${naming.present}
     [echo]   Tomcat resources.jar          ${resources.present}

With the following output you can check, whether the location is 
right.

  [echo] Library locations:
  [echo]   Servlet API jar               ./lib/servlet.jar
  [echo]   JAXP jar                      ./lib/jaxp.jar
  [echo]   XML DOM/SAX2 APIs jar         ./lib/crimson.jar
  [echo]   XML Parser jar                ./lib/crimson.jar
  [echo]   JTA jar                       ./lib/jta.jar
  [echo]   JDOM jar                      ./lib/jdom-dev.jar
  [echo]   Commons-Httpclient jar        lib/commons-httpclient.jar
  [echo]   Commons-Logging jar           ./lib/commons-logging.jar
  [echo]   ANTLR jar                     ./lib/antlr.jar
  [echo]   JDBC 2.0 optional package jar ./lib/jdbc2_0-stdext.jar
  [echo]   JMX jar                       ${jmx.jar}
  [echo]   Commons-Modeler jar           ./lib/commons-modeler.jar
  [echo]   Ant jar                       ../ant/lib/ant.jar
  [echo]   JUnit jar                     ./lib/junit.jar
  [echo]   Log4J jar                     ./lib/log4j.jar


I recommend, you edit build.properties and put the libraries to 
a place, where they can stay. If done so, all you need to do is 
copy your build.properties to another Slide directory, next time 
you pull the whole thing from CVS again. I did this, because I 
always download the 50MB in the university, take them home and 
have a new Slide directory. With this build.properties file I 
don't have to do the detection again and again.

Build.xml doesn't have the dependency on commons-logging.jar 
yet. I provided a patch, but it hasn't been applied yet. If you 
need the client API, make sure you copy commons-logging.jar to 
your client/lib directory. Otherwise the client can't run. If 
you need the client API you will also need it.

Andreas

> 
> --
> Sung Kim, UCSC
> 
> 


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>