|
I just finished working through some problems getting cocoon installed on my system. I found them to be rather odd, so I figured I'd bring it to the group's attention.
I believe everything in my configuration is about as current as could be, as I recently had to reinstall W2K:
Windows 2000 SP4
Apache 2.0.47
Ant 1.5.3
Tomcat 4.1.27
Cocoon 2.1.1 "latest"
After confirming that Apache, Ant, and Tomcat all installed properly, I unzipped Cocoon and followed the simplistic directions in the file "Install.txt" to complete my installation. (I typed "build") When I ran the build, I received this error:
BUILD FAILED file:C:/cocoon-2.1.1/build/cocoon-2.1.1/temp/blocks-build.xml:1542: C:\cocoon-2. 1.1\src\blocks\session-fw\lib not found.
To try to get around this problem, I decided to simply create the folder that was "not found", and try again. I then got a similar message with a different folder, and repeated my steps, creating another "lib" folder. I repeated this process roughly 20 times before I finally got a successful build. In all but one instance I needed to add a "lib" folder. In one case, I needed to add a "java" folder. If need be, I can hunt down all the specific folder names, but I doubt if that is an issue. Apparently, the problem is that the build tool is failing (in some cases) when a folder is missing, even if there is no required content in that folder.
The only thing even remotely out of the ordinary in my installation procedure that I can think of is that Tomcat wasn't running the first time I tried the "build" command. I can't see how that could have caused problems such as I described.
I just wanted to bring this to the group's attention, in case anyone else has run into similar problems, or if anyone can identify a "heads up" as to other problems that I need to be aware of as a result of these quirks. |
