Joerg, Thanks for the thorough response. Your explanation of the srcdir attribute certainly helps clarify my misdiagnosis of the problem. Funnily enough, your comments also suggested that the problem actually is driven by the fact that I had my cocoon base directory too deep within the directory structure. Placing cocoon at "D:\" shortened the path length sufficiently to enable the xpatch task to complete successfully. I am entirely unclear on whether this is an xpatch issue or a Windows 2000 issue or a Geoff Shuetrim issue but there we have it.
Thanks for this help in getting started with Cocoon! Geoff S > -----Original Message----- > From: Joerg Heinicke [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 31, 2004 9:10 AM > To: [EMAIL PROTECTED] > Subject: Re: xpatch srcdir attribute problems when building > Cocoon 2.1.4 > using Ant 1.6.1 and JDK 1.4.2_04 on Windows 2000 > > > On 30.03.2004 12:56, Geoff wrote: > > > 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. > > AFAIK only JAVA_HOME is needed. > > > 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. > > I never heard of such problems. And I'm also using Cocoon 2.1 on Win > 2000 on different machines. > > > Created dir: D:\Documents and Settings\gshuetrim\My > > Documents\cocoon-2.1.4\build\cocoon-2.1.4 > > ... > > > compile-deprecated: > > [mkdir] Created dir: D:\Documents and Settings\gshuetrim\My > > > Documents\Activities\Galexy\Activities\java\cocoon\build\cocoo > n-2.1.4\deprec > > ated > > [xpatch] Processing: D:\Documents and Settings\gshuetrim\My > > > Documents\Activities\Galexy\Activities\java\cocoon\src\depreca > ted\conf\depre > > cated.xroles > > [xpatch] Writing: D:\Documents and Settings\gshuetrim\My > > > Documents\Activities\Galexy\Activities\java\cocoon\build\cocoo > n-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\targe > ts\compile-bui > > ld.xml:55: TransformerException: > javax.xml.transform.TransformerException: > > Invalid syntax for base URI > > The output should look like the following: > > Created dir: D:\cocoon-2.1\build\cocoon-2.1.5-dev > > ... > > compile-deprecated: > Created dir: D:\cocoon-2.1\build\cocoon-2.1.5-dev\deprecated > Processing: D:\cocoon-2.1\src\deprecated\conf\deprecated.xroles > Writing: > D:\cocoon-2.1\build\cocoon-2.1.5-dev\classes\org\apache\cocoon > \cocoon.r > oles > Compiling 61 source files to > D:\cocoon-2.1\build\cocoon-2.1.5-dev\deprecated > > As you can see your target directory for the deprecated stuff is > completely wrong. It should be D:\Documents and Settings\gshuetrim\My > Documents\cocoon-2.1.4\build\cocoon-2.1.4\deprecated. Have > you something > reconfigured/changed in build.properties or local.build.properties? > Where does "Activities\Galexy\Activities\" come from? This part is > completely wrong. > > > 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\apac > he\cocoon\coco > > on.roles > > which is obviously? non-existent. > > No the @file is not resolved relative the @srcdir, but to > current build > base path. Only @includes are resolved relative to @srcdir as > from there > the patches are coming from. The @file file is patched. > > Joerg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
