Re: [t4] FYI: usual problems building according to README...
We're planning to do that, actually, and we're waiting a bit before removing the outdated scripts. fair enough. I always seem to run in to things like that when I build from source. To be expected I suppose... I don't suppose now I've got your attention you'd like to comment on the Jasper calling response.flushBuffer() when included from servlet problem I reported the other day??? :-) Its really bugging me not knowing if it's a bug or I'm missing something... I didn't comment, because I have no idea what to answer. I know very little about Jasper. fair enough! spose I should look through CVS to see whos got their paw prints on the 4.0 Jasper mods ... ;-) thanks geoff
Re: [t4] FYI: usual problems building according to README...
On Fri, 15 Jun 2001, Geoff Soutter wrote: Hi tc4 people, I'm putting myself through the regular build TC4 from source hell that I do whenever I want to test the latest version. (this is on WinNT4) I came across the following issues, you may be aware of them already but I thought I'd report 'em just in case... 1) It no longer builds on JDK1.2. The README indicates 1.2 or later is required. Yep ... that's a known issue with the new CGI support. It will get set up so that this is (at least) optional until we resolve the underlying dependency. I get the following errors on build dist for tomcat: build-main: [javac] Compiling 2 source files to D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\catalina\build\classes [javac] D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\catalina\src\share\org\apache\ca talina\servlets\CGIServlet.java:1567: Wrong number of arguments in metho d. [javac] proc = rt.exec(cmdAndArgs.toString(), hashToStringArray(env), wd); [javac] ^ [javac] D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\catalina\src\share\org\apache\ca talina\util\ProcessHelper.java:381: Wrong number of arguments in method. [javac] proc = rt.exec(cmdAndArgs.toString(), hashToStringArray(env), wd); [javac] ^ [javac] 2 errors BUILD FAILED Seems it's relying on a Runtime.exec() method overload which was added in JDK1.3 (interesting, the @since tag is missing? weird. Hope I'm not suffering brain-fade on this one...) 2) it seems to be depending on old versions of the projects it depends on: For example, the bootstrap.bat file for building jakarta-ant from source doesn't co-operate well with the other stuff. It sets - ANT_HOME=. - stuffs up the classpath (adds extra 's in there) - puts ant.jar in /bootstrap/lib rather than /lib where the other build scripts expect it. The revised instructions say to use a released version of Ant that has $ANT_HOME/bin on your PATH. Then, you can just say ant dist or whatever. Also, jakarta-regexp currently builds jakarta-regexp-1.3-dev.jar rather than the jakarta-regexp-1.2.jar that the catalina build.xml expects. Seems you can just rename the jar file or I guess you could use cvs checkout -r RELEASE_1_2 jakarta-regexp Classic reason I think putting version numbers in JAR filenames is not the right answer ... The other alternative (just copy all the JARs from that directory) runs the risk of getting multiple copies. 3) seems theres co-ordination problem between the jakarta-servletapi-4 and jakarta-tomcat. When I build I get the following error: BUILD FAILED D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\build.xml:129: D:\apps\jakarta\src\40b5\jakarta-servletapi-4\docs\api not found. build dist for the servlet API does create javadoc, but they are in the dist\docs\api dir... You need to do a ant dist in jakarta-servletapi-4 to create the API docs. I'll add that to the How To stuff. Apart from that it went well though :-) I'm cookin' with gas now... Geoff -- Keep cool till after school! Craig
[t4] FYI: usual problems building according to README...
Hi tc4 people, I'm putting myself through the regular build TC4 from source hell that I do whenever I want to test the latest version. (this is on WinNT4) I came across the following issues, you may be aware of them already but I thought I'd report 'em just in case... 1) It no longer builds on JDK1.2. The README indicates 1.2 or later is required. I get the following errors on build dist for tomcat: build-main: [javac] Compiling 2 source files to D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\catalina\build\classes [javac] D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\catalina\src\share\org\apache\ca talina\servlets\CGIServlet.java:1567: Wrong number of arguments in metho d. [javac] proc = rt.exec(cmdAndArgs.toString(), hashToStringArray(env), wd); [javac] ^ [javac] D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\catalina\src\share\org\apache\ca talina\util\ProcessHelper.java:381: Wrong number of arguments in method. [javac] proc = rt.exec(cmdAndArgs.toString(), hashToStringArray(env), wd); [javac] ^ [javac] 2 errors BUILD FAILED Seems it's relying on a Runtime.exec() method overload which was added in JDK1.3 (interesting, the @since tag is missing? weird. Hope I'm not suffering brain-fade on this one...) 2) it seems to be depending on old versions of the projects it depends on: For example, the bootstrap.bat file for building jakarta-ant from source doesn't co-operate well with the other stuff. It sets - ANT_HOME=. - stuffs up the classpath (adds extra 's in there) - puts ant.jar in /bootstrap/lib rather than /lib where the other build scripts expect it. Also, jakarta-regexp currently builds jakarta-regexp-1.3-dev.jar rather than the jakarta-regexp-1.2.jar that the catalina build.xml expects. Seems you can just rename the jar file or I guess you could use cvs checkout -r RELEASE_1_2 jakarta-regexp 3) seems theres co-ordination problem between the jakarta-servletapi-4 and jakarta-tomcat. When I build I get the following error: BUILD FAILED D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\build.xml:129: D:\apps\jakarta\src\40b5\jakarta-servletapi-4\docs\api not found. build dist for the servlet API does create javadoc, but they are in the dist\docs\api dir... Apart from that it went well though :-) I'm cookin' with gas now... Geoff -- Keep cool till after school!
Re: [t4] FYI: usual problems building according to README...
Hi tc4 people, I'm putting myself through the regular build TC4 from source hell that I do whenever I want to test the latest version. (this is on WinNT4) It's a lot easier now, actually :) I came across the following issues, you may be aware of them already but I thought I'd report 'em just in case... 1) It no longer builds on JDK1.2. The README indicates 1.2 or later is required. Yes indeed. It will be fixed. 2) it seems to be depending on old versions of the projects it depends on: It looks like you're still using the build scripts. You shouldn't. Instead, you should run Ant directly, and use a build.properties file. It's really a lot easier. 3) seems theres co-ordination problem between the jakarta-servletapi-4 and jakarta-tomcat. When I build I get the following error: BUILD FAILED D:\apps\jakarta\src\40b5\jakarta-tomcat-4.0\build.xml:129: D:\apps\jakarta\src\40b5\jakarta-servletapi-4\docs\api not found. build dist for the servlet API does create javadoc, but they are in the dist\docs\api dir... Apart from that it went well though :-) I'm cookin' with gas now... I think that's caused by 2) Remy
Re: [t4] FYI: usual problems building according to README...
Hi remy, Thanks for the reply. It's a lot easier now, actually :) It wasn't that hard b4, just the README was always a little out of date... 2) it seems to be depending on old versions of the projects it depends on: It looks like you're still using the build scripts. You shouldn't. Instead, you should run Ant directly, and use a build.properties file. It's really a lot easier. Don't give me that much credit :-). I'm just following the instructions... if I ought to be running Ant directly, then the instructions should say that ... :-) I don't suppose now I've got your attention you'd like to comment on the Jasper calling response.flushBuffer() when included from servlet problem I reported the other day??? :-) Its really bugging me not knowing if it's a bug or I'm missing something... Geoff
Re: [t4] FYI: usual problems building according to README...
Hi remy, Thanks for the reply. It's a lot easier now, actually :) It wasn't that hard b4, just the README was always a little out of date... 2) it seems to be depending on old versions of the projects it depends on: It looks like you're still using the build scripts. You shouldn't. Instead, you should run Ant directly, and use a build.properties file. It's really a lot easier. Don't give me that much credit :-). I'm just following the instructions... if I ought to be running Ant directly, then the instructions should say that ... :-) We're planning to do that, actually, and we're waiting a bit before removing the outdated scripts. I don't suppose now I've got your attention you'd like to comment on the Jasper calling response.flushBuffer() when included from servlet problem I reported the other day??? :-) Its really bugging me not knowing if it's a bug or I'm missing something... I didn't comment, because I have no idea what to answer. I know very little about Jasper. Remy
