Mailing-List: contact taglibs-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: taglibs-dev@jakarta.apache.org
Date: Tue, 28 Aug 2001 04:14:00 +0100 (BST)
From: bayard@generationjava.com
To: taglibs-dev@jakarta.apache.org
Subject: Re: Build help
In-Reply-To: <069501c12bd1$d26ad320$9865fea9@spiritsoft.com>
Message-ID: <Pine.LNX.4.21.0108280402100.2433-100000@umbongo.flamefew.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Time for me to whine annoyingly again :)

ant.jar 1.3 and the optional.jar both added to the classpath.
ant shell script placed in my command path.

now I get told about some problems with TransformerFactory and its ilk.

install xalan.jar after making the diagnosis that some xsl was going
on. add xerces.jar too. and xml.jar.

currently getting:

template-tld11:
    [style] Transforming into
/home/hen/jakarta/jakarta-taglibs/build/string/string-examples/WEB-INF
    [style] Loading stylesheet
/home/hen/jakarta/jakarta-taglibs/string/../src/taglib/tld11.xsl
    [style] Failed to read stylesheet ../src/taglib/tld11.xsl

followed by a handful of:

javax.xml.parsers.ParserConfigurationException: Namespace not supported by
SAXParser 

So I guess my parser.jar is out of date? Anyone know where to get a modern
SAX parser from?

Dunno if it helps, but here's the list of things in my classpath.

/usr/lib/java/jre/lib/rt.jar
/usr/lib/java/lib/tools.jar
.
/usr/local/share/jedit/3.2pre1/jedit.jar
/usr/lib/javalib/ant.jar
/usr/lib/javalib/cfparse.jar
/usr/lib/javalib/collections.jar
/usr/lib/javalib/jakarta-ant-1.3-optional.jar
/usr/lib/javalib/jaxp.jar
/usr/lib/javalib/parser.jar
/usr/lib/javalib/servlet.jar
/usr/lib/javalib/xalan.jar
/usr/lib/javalib/xerces.jar
/usr/lib/javalib/xml.jar


I get the same error when I try to build string, random or request. (didnt
try others). The tld11.xsl exists fine, all dirs have read and execute,
and all files have read.

Thanks

Bay

On Thu, 23 Aug 2001, James Strachan wrote:

> Try using the proper 1.3 release of Ant (and make sure you use the
> optional.jar from the 1.3 release) and see how you get on.
> 
> James
> ----- Original Message -----
> From: <bayard@generationjava.com>
> To: <taglibs-dev@jakarta.apache.org>
> Sent: Thursday, August 23, 2001 1:49 PM
> Subject: Build help
> 
> 
> > Sorry to be a burden. Am currently hitting errors in Ant and wondering
> > which particular part I've cocked up.
> >
> > I'm using "Ant version 1.3alpha compiled on December 11 2000", is this
> > horribly old?
> >
> > I have an alias of   alias ant='java org.apache.tools.ant.Main'
> >
> > I've generated out my default directory using the ant new.taglib task.
> >
> > Have modified said files and am trying to run the ant alias in my
> > taglib directory.  This is not very happy. I've modified build.properties
> > to fit my environment. I get the following error on running 'ant'.
> >
> > ============
> > Buildfile: build.xml
> > Property ${javalib.dir} has not been set
> > Property ${servlet.jar} has not been set
> > Property ${base.dir} has not been set
> > Property ${base.dir} has not been set
> > Property ${taglib-doc.dir} has not been set
> > Property ${build.examples} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib-doc.dir} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib-doc.dir} has not been set
> > Property ${taglib-doc.dir} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${build.library} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> > Property ${taglib.name} has not been set
> >
> > BUILD FAILED
> >
> > /home/hen/jakarta/jakarta-taglibs/string/build.xml:103: Class
> > org.apache.tools.ant.taskdefs.XSLTProcess doesn't support the nested
> > "param" element
> >
> >
> > I've looked at ant -verbose and ant -debug, but all they seem to do is
> > suggest that the unset Propertys get set right after the 'has not been
> > set' messages. It also will occasionally mention that an override has been
> > ignored.
> >
> > I get the same thing if I try to do a build on the random taglib, so I'm
> > assuming it's an issue with my setup. Has anyone seen this before?
> >
> > Thanks
> >
> > Bay
> >
> >
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
>