avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Randall" <crand...@tivre.com>
Subject RE: LogKit doesn't build
Date Thu, 09 May 2002 15:26:43 GMT
I do have two separate JDK installations on my machine. But, the JAVA_HOME PATH variable that
Ant uses most definitely resolves to the JDK 1.3.1 directory.

I did a search, and there is NO jdbc2_0-stdext.jar ANYWHERE in the JDK 1.3.1 path structure.

Is there any issue with the sql-warn target if the framework-warn task shows that it cannot
locate the framework JAR file? Will it continue through the processing of other "available"
tasks if one fails?

-----Original Message-----
From: Peter Donald [mailto:peter@apache.org]
Sent: Wednesday, May 08, 2002 2:15 PM
To: Avalon Developers List
Subject: Re: LogKit doesn't build


Hi,

This is wierd. Are you sure you don't have the jdbc2_0-stdext.jar installed 
somewhere else? Perhaps in your ext/ dir in your JVM? 

The reason I say this is that the <available ../> task checks for the presence 
of jdbc and if it is not present will issue a warning. But if you see below 
the target "sql-warn" was silent which implies it found the class.

Have you only got 1 JVM on your machine? I had a similar problem when I used 
java from one JVM but javac from another JVM was in path beforehand.

On Thu, 9 May 2002 04:37, Christopher Randall wrote:
> I have include the text of the Ant logfile from my build:
> ---------------------------------------------------------------------------
>-- Buildfile: build.xml
>
> optional-tests:
>
> jms-warn:
>
> op-warning:
>      [echo] **********************************************
>      [echo] *
>      [echo] *  Classes needed for output via JMS are not
>      [echo] *  available.  Logkit should build without them
>      [echo] *
>      [echo] *  Recovery:
>      [echo] *  Get jms.jar from inside jms-1_0_2b.zip from
> http://java.sun.com/products/jms/docs.html and place it in the lib dir
> [echo] *
>      [echo] ***********************************************
>      [echo]
>
> framework-warn:
>      [echo] **********************************************
>      [echo] *
>      [echo] *  Optional classes from Avalon's framework subproject
>      [echo] *  are missing.  Logkit should build without them.
>      [echo] *
>      [echo] *  Run the build target import-framework-jar and it will
>      [echo] *  get the framework jar from a relative directory if there.
>      [echo] *
>      [echo] ***********************************************
>      [echo]
>
> sql-warn:
>
> servlet-warn:
>
> op-warning:
>      [echo] **********************************************
>      [echo] *
>      [echo] *  Classes needed for output via Servlet are not
>      [echo] *  available.  Logkit should build without them
>      [echo] *
>      [echo] *  Recovery:
>      [echo] *  Run the build target import-servlet-jar and it will download
> the servlet api jar - you should be online for that. [echo] *
>      [echo] ***********************************************
>      [echo]
>
> optional-warnings:
>
> compile:
>     [mkdir] Created dir: /home/crandall/avalon/LogKit-1.0.1/build
>     [mkdir] Created dir: /home/crandall/avalon/LogKit-1.0.1/build/classes
>     [javac] Compiling 59 source files to
> /home/crandall/avalon/LogKit-1.0.1/build/classes [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Abstra
>ctJDBCTarget.java:12: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: package sql
>     [javac] import javax.sql.DataSource;
>     [javac]                  ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Abstra
>ctJDBCTarget.java:25: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: class org.apache.log.output.db.AbstractJDBCTarget
>     [javac]     private DataSource     m_dataSource;
>     [javac]             ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Abstra
>ctJDBCTarget.java:30: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: class org.apache.log.output.db.AbstractJDBCTarget
>     [javac]     protected AbstractJDBCTarget( final DataSource dataSource )
>     [javac]                                         ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Defaul
>tDataSource.java:14: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: package sql
>     [javac] import javax.sql.DataSource;
>     [javac]                  ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Defaul
>tDataSource.java:23: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: class org.apache.log.output.db.DefaultDataSource
>     [javac]     implements DataSource
>     [javac]                ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Defaul
>tJDBCTarget.java:15: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: package sql
>     [javac] import javax.sql.DataSource;
>     [javac]                  ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Defaul
>tJDBCTarget.java:33: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: class org.apache.log.output.db.DefaultJDBCTarget
>     [javac]     public DefaultJDBCTarget( final DataSource dataSource,
>     [javac]                                     ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Normal
>izedJDBCTarget.java:15: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: package sql
>     [javac] import javax.sql.DataSource;
>     [javac]                  ^
>     [javac]
> /home/crandall/avalon/LogKit-1.0.1/src/java/org/apache/log/output/db/Normal
>izedJDBCTarget.java:33: cannot resolve symbol [javac] symbol  : class
> DataSource
>     [javac] location: class org.apache.log.output.db.NormalizedJDBCTarget
>     [javac]     public NormalizedJDBCTarget( final DataSource dataSource,
>     [javac]                                        ^
>     [javac] 9 errors
>
> BUILD FAILED
>
> /home/crandall/avalon/LogKit-1.0.1/build.xml:262: Compile failed, messages
> should have been provided.
>
> Total time: 4 seconds
>
> ---------------------------------------------------------------------------
>--
>
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: Wednesday, May 08, 2002 11:30 AM
> To: 'Avalon Developers List'
> Subject: RE: LogKit doesn't build
>
> > From: Christopher Randall [mailto:crandall@tivre.com]
> >
> > I unzipped the LogKit src zip file to my local machine, and
> > ran the Ant script, and the build fails right off the bat.
> >
> > The build script is warning me that a bunch of files are
> > missing. Why does this happen? Why are the required files not
> > included in the LogKit src ZIP file? I am not required to
> > download a bunch of files when I build from the other Avalon
> > source ZIP files.
>
> LogKit has some _optional_ targets that it can send log messages
> to if the jars are included.  The licensing for those jars
> precludes us from including them:
>
> JMS (Java Messaging Service) target,
> JDBC (Database) target,
> Servlet target (delegates to the servlet context's log method),
> JavaMail target.
>
> LogKit should be able to build if you do not have any of these
> jars or apis in your classpath.
>
> If it does not build, I would like to know what additional
> jars it says you need.

-- 
Cheers,

Peter Donald


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message