The recent change to the project.xml of the ant taglib causes an issue
with Xerces under jdk1.3.1 on my machine.
Building with JDK 1.4.1 works fine, other than the failing test in the
html taglib I added yesterday.
Here's the JDK1.3 stacktrace:
------>8---------------------------
C:\source\jakarta\jakarta-commons-sandbox\jelly>set
JAVA_HOME=c:\jdk1.3.1_06
C:\source\jakarta\jakarta-commons-sandbox\jelly>maven -e tags-build
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-8
Attempting to download commons-cli-SNAPSHOT.jar.
Attempting to download commons-lang-SNAPSHOT.jar.
Attempting to download commons-discovery-SNAPSHOT.jar.
Starting the reactor ...
BUILD FAILED
java.net.UnknownHostException: C
at java.net.InetAddress.getAllByName0(InetAddress.java:566)
at java.net.InetAddress.getAllByName0(InetAddress.java:535)
at java.net.InetAddress.getByName(InetAddress.java:444)
at java.net.Socket.<init>(Socket.java:95)
at sun.net.NetworkClient.doConnect(NetworkClient.java:45)
at sun.net.NetworkClient.openServer(NetworkClient.java:33)
at sun.net.ftp.FtpClient.openServer(FtpClient.java:262)
at sun.net.ftp.FtpClient.<init>(FtpClient.java:376)
at
sun.net.www.protocol.ftp.FtpURLConnection.connect(FtpURLConnection.ja
va:72)
at
sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnec
tion.java:91)
at java.net.URL.openStream(URL.java:793)
at
org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.
java:796)
at
org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.
java:725)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEntityRefer
ence(XMLDocumentFragmentScannerImpl.java:1073)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1489)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XM
LDocumentFragmentScannerImpl.java:333)
at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.jav
a:524)
at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.jav
a:580)
at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.j
ava:1169)
at org.apache.commons.digester.Digester.parse(Digester.java:1266)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:192)
------>8---------------------------
And the jdk1.4 starting fine:
------>8---------------------------
C:\source\jakarta\jakarta-commons-sandbox\jelly>set
JAVA_HOME=c:\j2sdk1.4.1_01
C:\source\jakarta\jakarta-commons-sandbox\jelly>maven -e tags-build
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-beta-8
Attempting to download commons-cli-SNAPSHOT.jar.
Attempting to download commons-lang-SNAPSHOT.jar.
Attempting to download commons-discovery-SNAPSHOT.jar.
Starting the reactor ...
Our processing order:
commons-jelly-tags-soap
commons-jelly-tags-junit
commons-jelly-tags-util
commons-jelly-tags-threads
commons-jelly-tags-xml
commons-jelly-tags-antlr
commons-jelly-tags-dynabean
commons-jelly-tags-log
commons-jelly-tags-define
commons-jelly-tags-http
commons-jelly-tags-jetty
commons-jelly-tags-swing
commons-jelly-tags-betwixt
commons-jelly-tags-sql
commons-jelly-tags-swt
commons-jelly-tags-xmlunit
commons-jelly-tags-ant
commons-jelly-tags-jsl
commons-jelly-tags-html
commons-jelly-tags-bsf
commons-jelly-tags-jms
commons-jelly-tags-email
commons-jelly-tags-beanshell
commons-jelly-tags-fmt
commons-jelly-tags-ojb
commons-jelly-tags-quartz
commons-jelly-tags-bean
commons-jelly-tags-validate
commons-jelly-tags-velocity
commons-jelly-tags-interaction
------>8---------------------------
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Morgan Delagrange <[EMAIL PROTECTED]> wrote on 21/01/2003 04:08:05 AM:
>
> --- James Strachan <[EMAIL PROTECTED]> wrote:
> >
> > I'm gonna sit on the fence a little as I agree with
> > both of you. Before a
> > 1.0 release I'd like to
> >
> > * provide a simple build to build and test all the
> > libraries (hopefully
> > using Maven reactor though anything would do). This
> > can help in refactoring,
> > testing that we don't break things.
>
> Everything appears to be correct in the reactor. I
> verified via debug statements that the parse fails
> when MavenUtils.getProject(File, MavenJellyContext,
> boolean) attempts to parse the projectDescriptor with
> Betwixt via the BeanReader.parse(File) method. That
> method seems to be inherited from Digester, and looks
> fine:
>
> public Object parse(File file)
> throws IOException, SAXException {
> configure();
> InputSource input =
> new InputSource(new FileInputStream(file));
> input.setSystemId("file://" +
> file.getAbsolutePath());
> getXMLReader().parse(input);
> return (root);
> }
>
> Wierd.
>
> > * fix the tag reference documentation build process,
> > both as reference
> > documentation is very useful and that the current
> > hacked-together-doclet
> > causes a dependency of the core Jelly jar on javadoc
> > and nekohtml. Moving
> > this into (say) a Maven plugin seems like a good
> > idea
> >
> > James
>
> Sounds good.
>
> - Morgan
>
> =====
> Morgan Delagrange
> http://jakarta.apache.org/taglibs
> http://jakarta.apache.org/commons
> http://axion.tigris.org
> http://jakarta.apache.org/watchdog
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
> ForwardSourceID:NT000A5A42
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
