I think the problem was an old release of jdk1.3.  I updated to the latest
release from sun.com (1.3.1.04) and the build was successful.

Geoff

> -----Original Message-----
> From: Geoff Howard 
> Sent: Thursday, August 01, 2002 4:29 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Build Trouble
> 
> 
> oops, forgot to provide the errors:
> 
> compile:
>      [copy] Copying 28 files to 
> C:\cocoon\cocoon-2.0.3\build\cocoon\classes
>      [echo] Compiling with Java 1.3, debug on, optimize off, 
> deprecation off
>     [javac] Compiling 609 source files to
> C:\cocoon\cocoon-2.0.3\build\cocoon\classes
>     [javac]
> C:\cocoon\cocoon-2.0.3\build\cocoon\src\org\apache\cocoon\comp
> onents\languag
> e\generator\GeneratorSelector.java:129: cannot resolve symbol
>     [javac] symbol  : method setLoggerManager
> (org.apache.avalon.excalibur.logger.LoggerManager)
>     [javac] location: class
> org.apache.avalon.excalibur.component.ExcaliburComponentSelector
>     [javac]         super.setLoggerManager(logkit);
>     [javac]              ^
>     [javac]
> C:\cocoon\cocoon-2.0.3\build\cocoon\src\org\apache\cocoon\comp
> onents\languag
> e\generator\GeneratorSelector.java:186: cannot resolve symbol
>     [javac] symbol  : method getLogkitLogger  ()
>     [javac] location: class
> org.apache.cocoon.components.language.generator.GeneratorSelector
>     [javac]             handler.setLogger(getLogkitLogger());
>     [javac]                               ^
>     [javac]
> C:\cocoon\cocoon-2.0.3\build\cocoon\src\org\apache\cocoon\comp
> onents\languag
> e\programming\java\JavaProgram.java:89: cannot resolve symbol
>     [javac] symbol  : method getComponentHandler
> (java.lang.Class,org.apache.avalon.framework.configuration.Def
> aultConfigurat
> ion,org.apache.avalon.fr
> amework.component.ComponentManager,org.apache.avalon.framework
> .context.Conte
> xt,org.apache.avalon.excalibur.component.RoleManager,org.apach
> e.avalon.exc
> alibur.component.LogkitLoggerManager)
>     [javac] location: class
> org.apache.avalon.excalibur.component.ComponentHandler
>     [javac]         return ComponentHandler.getComponentHandler(
>     [javac]                                ^
>     [javac]
> C:\cocoon\cocoon-2.0.3\build\cocoon\src\org\apache\cocoon\comp
> onents\languag
> e\programming\javascript\JavascriptProgram.java:109: cannot re
> solve symbol
>     [javac] symbol  : method getComponentHandler
> (java.lang.Class,org.apache.avalon.framework.configuration.Def
> aultConfigurat
> ion,org.apache.avalon.fr
> amework.component.ComponentManager,org.apache.avalon.framework
> .context.Conte
> xt,org.apache.avalon.excalibur.component.RoleManager,org.apach
> e.avalon.exc
> alibur.component.LogkitLoggerManager)
>     [javac] location: class
> org.apache.avalon.excalibur.component.ComponentHandler
>     [javac]         return ComponentHandler.getComponentHandler(
>     [javac]                                ^
>     [javac]
> C:\cocoon\cocoon-2.0.3\build\cocoon\src\org\apache\cocoon\xml\
> dom\SVGBuilder
> .java:85: cannot resolve symbol
>     [javac] symbol  : method setCSSParserClassName  (java.lang.String)
>     [javac] location: class 
> org.apache.batik.util.XMLResourceDescriptor
>     [javac]
> XMLResourceDescriptor.setCSSParserClassName(CSS_PARSER_CLASS_NAME);
>     [javac]                              ^
>     [javac] 5 errors
> 
> BUILD FAILED
> 
> C:\cocoon\cocoon-2.0.3\build.xml:954: Compile failed, 
> messages should have
> been provided.
> 
> Total time: 1 minute 59 seconds
> 
> > -----Original Message-----
> > From: Geoff Howard 
> > Sent: Thursday, August 01, 2002 4:24 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: Build Trouble
> > 
> > 
> > I have been using the HEAD branch from CVS, but have just 
> > downloaded a copy
> > of the 2.0.3 source distribution and have been unable to build.
> > 
> > I'm using JDK 1.3.1 on Win2k
> > with the command: build -Dinclude.webapp.libs=yes
> > -Dinstall.war=%TOMCAT_HOME%\webapps webapp
> > where %TOMCAT_HOME% evaluates to c:\jakarta-tomcat-4.0, which 
> > is my correct
> > installation.
> > 
> > As I said, I already have a version of Cocoon 2.1-dev built 
> > and running, but
> > don't see why that would affect anything.  I've used build 
> > clean after 
> > each failed attempt.
> > 
> > Any ideas?  I haven't seen any complaints about this on either list.
> > 
> > Geoff Howard
> > 
> > 
> ---------------------------------------------------------------------
> > Please check that your question  has not already been 
> answered in the
> > FAQ before posting.     
> <http://xml.apache.org/cocoon/faq/index.html>
> > 
> > To unsubscribe, e-mail:     
> <[EMAIL PROTECTED]>
> > For additional commands, e-mail:   
> <[EMAIL PROTECTED]>
> > 
> 
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
> 
> To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>
> 

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to