You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by James Strachan <ja...@yahoo.co.uk> on 2001/08/23 14:47:51 UTC
Re: Build help
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: <ba...@generationjava.com>
To: <ta...@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
Re: Build help
Posted by Glenn Nielsen <gl...@voyager.apg.more.net>.
This can happen when using cvs to commit changes to files recently
imported. This is because the import didn't create CVS directories
in your local copy of the repository.
The fix:
mv the new imported directory to a temp directory name.
Then do a fresh checkout of the repository/directory.
There may be a better way around this problem, but the above works
for me.
Regards,
Glenn
bayard@generationjava.com wrote:
>
> > http://jakarta.apache.org/taglibs/sourcedist.html
> >
> > and added xalan.jar and xerces.jar into Ant's lib directory and it all
> > worked fine.
>
> getting jaxp1.1 solved my problems. Built happily, added apache licence
> header and started cvs adding directories. (sorry for the email spam).
>
> However, I get cvs lock issues to commit anything but the build.xml in my
> top dir.
>
> ****************
> cvs commit xml/intro.xml
>
> bayard@cvs.apache.org's password:
>
> cvs server: failed to create lock directory for
> `/home/cvs/jakarta-taglibs/string/xml'
> (/home/cvs/jakarta-taglibs/string/xml/#cvs.lock): No such file or
> directory
> cvs server: lock failed - giving up
> cvs [server aborted]: lock failed - giving up
> *****************
>
> Any ideas? My initial guess would be that my user hasn't got permission to
> create a #cvs.lock, I would assume because my user doesn't have a group
> set. But that's a guess :)
>
> Bay
--
----------------------------------------------------------------------
Glenn Nielsen glenn@more.net | /* Spelin donut madder |
MOREnet System Programming | * if iz ina coment. |
Missouri Research and Education Network | */ |
----------------------------------------------------------------------
Re: Build help
Posted by ba...@generationjava.com.
> http://jakarta.apache.org/taglibs/sourcedist.html
>
> and added xalan.jar and xerces.jar into Ant's lib directory and it all
> worked fine.
getting jaxp1.1 solved my problems. Built happily, added apache licence
header and started cvs adding directories. (sorry for the email spam).
However, I get cvs lock issues to commit anything but the build.xml in my
top dir.
****************
cvs commit xml/intro.xml
bayard@cvs.apache.org's password:
cvs server: failed to create lock directory for
`/home/cvs/jakarta-taglibs/string/xml'
(/home/cvs/jakarta-taglibs/string/xml/#cvs.lock): No such file or
directory
cvs server: lock failed - giving up
cvs [server aborted]: lock failed - giving up
*****************
Any ideas? My initial guess would be that my user hasn't got permission to
create a #cvs.lock, I would assume because my user doesn't have a group
set. But that's a guess :)
Bay
Re: Build help
Posted by James Strachan <ja...@yahoo.co.uk>.
----- Original Message -----
From: <ba...@generationjava.com>
To: <ta...@jakarta.apache.org>
Sent: Tuesday, August 28, 2001 4:14 AM
Subject: Re: Build help
> 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
Yes - this usually means that an old parser is not on the classpath - or
that no JAXP compliant parser is available.
I'd get a recent copy of JAXP 1.1 and use the xalan.jar and crimson.jar from
there. Or just upgrade your xerces.jar would do it as well.
What version of Xerces have you got - maybe its an old, pre JAXP support
version? These days I think xerces.jar comes with JAXP support and the JAXP
classes too.
> 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
A recent xerces.jar should fix this anyways I think. I followed Glenn's
instructions here:-
http://jakarta.apache.org/taglibs/sourcedist.html
and added xalan.jar and xerces.jar into Ant's lib directory and it all
worked fine.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Re: Build help
Posted by ba...@generationjava.com.
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: <ba...@generationjava.com>
> To: <ta...@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
>
>