Summary: I've made it farther but am still having issues, this time
mainly with ant, along with some syntax errors in the Excalibur code.
What follows is the list of what I've run into, up to getting stuck when
ant (1.4.1) didn't like the build.xml syntax.
I still need some help, mainly with ant. You also may want to note the
Java code errors I found and patched.
More below.
- Jenny Brown
On Tue, 5 Nov 2002, Peter Donald wrote:
> > Maybe I am using a different version of log4j that this was built for?
> > I have log4j-1.2.6.jar in my classpath.
>
> Thats it. The version you are using was meant to be compiled against an
> earlier version of log4j (1.1.x I think). That latest excalibur has been
> updated to more recent Log4j version.
Ok, I just built a bunch of packages (avalon, logkit, several others)
from the current CVS versions. Lots of things compiled well and are
working for me. I'm still having a few issues with Excalibur build
though, and so far they all seem of the patchable type.
1) Problem with syntax in build.xml, error message says:
/home/jbrown/Excalibur-Devel/jakarta-avalon-excalibur/info/build.xml:152:
The <javadoc> task doesn't support the nested "tag" element.
It's referring to <tag> in:
<javadoc packagenames="org.apache.*"
sourcepath="${java.dir}"
destdir="${dist.javadocs}">
<classpath refid="project.class.path" />
<group title="Info API" packages="org.apache.avalon.framework.info.*" />
<group title="Info Tools API" packages="org.apache.avalon.framework.tools.*" />
<tag name="todo" description="To do:" scope="all" />
<tag name="avalon.component" enabled="false" description="Component:" scope="types" />
<tag name="avalon.service" enabled="false" description="Service:" scope="types" />
<tag name="avalon.context" enabled="false" description="Context:" scope="methods" />
<tag name="avalon.entry" enabled="false" description="Context:" scope="methods" />
<tag name="avalon.dependency" enabled="false" description="Context:" scope="methods"
/>
<doclet name="com.sun.tools.doclets.standard.Standard">
<param name="-author"/>
<param name="-version"/>
<param name="-doctitle" value="${Name}"/>
<param name="-windowtitle" value="${Name} API"/>
<param name="-link" value="http://java.sun.com/j2se/1.4/docs/api/"/>
<param name="-link" value="http://java.sun.com/j2ee/sdk_1.3/techdocs/api/"/>
<param name="-link" value="http://jakarta.apache.org/avalon/api/"/>
<param name="-bottom"
value=""Copyright © ${year} Apache Jakarta Project. All Rights
Reserved.""/>
</doclet>
</javadoc>
This occurs in many build files actually, not just that subdirectory.
2) For the sake of progress I took out the javadoc tag lines completely and did
another build. This time it progressed farther, but still died out on
a compilation error, that seems to be the file simply missing an import
statement at the top ( import java.util.*; ):
/home/jbrown/Excalibur-Devel/jakarta-avalon-excalibur/datasource/build/src/org/apache/avalon/excalibur/datasource/AbstractJdbcConnection.java:45:
cannot resolve symbol
symbol : class Map
location: class org.apache.avalon.excalibur.datasource.AbstractJdbcConnection
protected Map m_statements;
^
/home/jbrown/Excalibur-Devel/jakarta-avalon-excalibur/datasource/build/src/org/apache/avalon/excalibur/datasource/AbstractJdbcConnection.java:126:
cannot resolve symbol
symbol : class Iterator
location: class org.apache.avalon.excalibur.datasource.AbstractJdbcConnection
Iterator it = m_statements.getKeySet().iterator();
3) Now that file tries to compile but still has errors:
/home/jbrown/Excalibur-Devel/jakarta-avalon-excalibur/datasource/build/src/org/apache/avalon/excalibur/datasource/AbstractJdbcConnection.java:127:
cannot resolve symbol
symbol : method getKeySet ()
location: interface java.util.Map
Iterator it = m_statements.getKeySet().iterator();
^
The correct method to call is .keySet() not .getKeySet() so I fix that
in the code and try again.
4) Now I get another build.xml issue (maybe I have the wrong ant
version? but I'm using the one from the avalon lib dir from cvs):
/home/jbrown/Excalibur-Devel/jakarta-avalon-excalibur/fortress/build.xml:99:
The <jar> task doesn't support the nested "zipgroupfileset" element.
<zipgroupfileset dir="${build.dir}/tempjars">
<include name="*.jar"/>
<include name="merlin*/*.jar"/>
</zipgroupfileset>
It also complains about destfile:
<jar destfile="${build.lib}/${name}-complete-${version}.jar">
At this point I'm sorta stuck since I'm wary of messing with how the
jarring occurs.
Here's my ant version:
[jbrown@henri jakarta-avalon-excalibur]$ ant -version
Ant version 1.4.1 compiled on October 11 2001
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
