I am trying to build and install Cocoon 2.1.4 on Windows 2000 to run under
Tomcat 5.0.19. I am pretty sure that I have configured my environment
variables for ANT_HOME, CATALINA_HOME and JAVA_HOME correctly.
Unfortunately, I am running into problems with getting the build to progress
past the fairly early stages. When trying to build Cocoon using the
build.bat batch file: the Ant reporting indicates a problem with the
configuration of xpatch tasks relating to the determination of the srcdir
attribute. The following ANT output explains this view.
[snip]
init-tasks:
Created dir: D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\tools\anttasks
Compiling 2 source files to D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\tools\anttasks
8 warnings
Created dir: D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\tools\loader
Compiling 1 source file to D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\tools\loader
prepare:
======================================================================
Apache Cocoon 2.1.4 [1999-2004]
======================================================================
Building with Apache Ant version 1.6.0 compiled on December 18 2003
----------------------------------------------------------------------
Using build file d:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\build.xml
----------------------------------------------------------------------
Compiler options:
- debug ......... [on]
- optimize ...... [on]
- deprecation ... [off]
======================================================================
Created dir: D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\build\cocoon-2.1.4
compile-core:
Copying 40 files to D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\build\cocoon-2.1.4\classes
Copied 70 empty directories to 37 empty directories under D:\Documents and
Settings\gshuetrim\My Documents\cocoon-2.1.4\build\cocoon-2.1.4\classes
Created dir: D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\build\cocoon-2.1.4\mocks
Compiling 1 source file to D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\build\cocoon-2.1.4\mocks
Compiling 563 source files to D:\Documents and Settings\gshuetrim\My
Documents\cocoon-2.1.4\build\cocoon-2.1.4\classes
compile-deprecated:
[mkdir] Created dir: D:\Documents and Settings\gshuetrim\My
Documents\Activities\Galexy\Activities\java\cocoon\build\cocoon-2.1.4\deprec
ated
[xpatch] Processing: D:\Documents and Settings\gshuetrim\My
Documents\Activities\Galexy\Activities\java\cocoon\src\deprecated\conf\depre
cated.xroles
[xpatch] Writing: D:\Documents and Settings\gshuetrim\My
Documents\Activities\Galexy\Activities\java\cocoon\build\cocoon-2.1.4\classe
s\org\apache\cocoon\cocoon.roles
BUILD FAILED
D:\Documents and Settings\gshuetrim\My
Documents\Activities\Galexy\Activities\java\cocoon\tools\targets\compile-bui
ld.xml:55: TransformerException: javax.xml.transform.TransformerException:
Invalid syntax for base URI
[snip]
Looking into line 55 of the compile-build.xml Ant file, I find:
<!-- compiles deprecated code -->
<target name="compile-deprecated" depends="prepare"
unless="unless.exclude.deprecated">
<mkdir dir="${build.deprecated}"/>
<xpatch file="${build.dest}/org/apache/cocoon/cocoon.roles"
srcdir="${deprecated.conf}"
includes="**/*.xroles"/> <!-- THIS IS THE CULPRIT -->
<javac srcdir="${deprecated.src}"
destdir="${build.deprecated}"
debug="${compiler.debug}"
optimize="${compiler.optimize}"
deprecation="${compiler.deprecation}"
target="${target.vm}"
compiler="${compiler}"
classpathref="classpath"/>
</target>
The value of the file attribute resolves to:
build\cocoon-2.1.4\classes\org\apache\cocoon\cocoon.roles
which exists when resolved from the project root directory.
The value of the srcdir attribute resolves to:
cocoon\src\deprecated\conf
which exists.
My reading of this is that the file gets looked for at:
cocoon\src\deprecated\conf\build\cocoon-2.1.4\classes\org\apache\cocoon\coco
on.roles
which is obviously? non-existent.
Are others having similar problems with the 2.1.4 release?
Do people have suggestions for how to ensure that the srcdir attribute is
left as ""?
If I configure the build to exclude the deprecated functionality I find that
I just run into the same kind of problem somewhat later in the build
process.
Regards
Geoff Shuetrim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
