Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 37971 invoked by uid 500); 15 Apr 2003 12:57:03 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 37939 invoked from network); 15 Apr 2003 12:57:03 -0000 Received: from smtp1.xs4all.be (195.144.64.135) by daedalus.apache.org with SMTP; 15 Apr 2003 12:57:03 -0000 Received: from outerthought.org (stat88-21.adsl.xs4all.be [195.144.88.21]) by smtp1.xs4all.be (8.12.9/8.12.9) with ESMTP id h3FCv2p5011985 for ; Tue, 15 Apr 2003 14:57:02 +0200 Message-ID: <3E9C019D.9030409@outerthought.org> Date: Tue, 15 Apr 2003 14:57:01 +0200 From: Marc Portier User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en, nl-be MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Code cosmetics (was: [GUMP] Build Failure - xml-forrest) Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi there, this sounds like a bit of an upcoming issue for a rather cosmetic change: http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/generation/FileGenerator.java.diff?r1=1.1&r2=1.2 (thx to Steven for helping me see the wonders of viewcvs) I would not like to just add the upcoming method as well and delegate to the old one since then we will just shut up gump and will loose his alarming function reminding us that we still have to remove the old signatures some time in future, right? So upgrading to cocoon-head once again seems appropriate, I'm getting into gear for doing the job, was just asking a number of things: I know I have been somewhat of this list lately, but your short answers can help me get the most of the effort I still want to share... 0. have any of you tried recently and are there issues? 1. do we have some minor standard procedure on how to build cocoon for forrest and test it? (or is there nothing specific to it) 2. how urgent do you guys feel this is? - I'ld like to clean up the depricate warnings as well, and it somewhat calls for a new version of the ComposerGenerator base class over at cocoon (will investigate that part of the cocoon branch to start a thread over there ) 3. Vaguely related: part of the code in scratchpad putting this on the agenda is the Libre stuff, since we have the site.xml there seems to be a number of new reasons to revive this thing (generation of that file for larger sites seems like a quick win?) But maybe that usage would rather push it into an Ant Task then a Cocoon Generator? Not to mention the fact that "we should ditch this code if there is no usage for it" (and better do that before people think I've parked it over here for you to maintain) So bluntly: Do we see usage? If yes, please elaborate and let's get to it, I'ld like to get in do-mode 'round this. regards, -marc= -------- Original Message -------- Subject: [GUMP] Build Failure - xml-forrest Date: 15 Apr 2003 10:26:54 -0000 From: Gump@icarus.apache.org Reply-To: forrest-dev@xml.apache.org To: forrest-dev@xml.apache.org ---------------------------------------------------- This email is autogenerated from the output from: ---------------------------------------------------- Buildfile: build.xml init: [echo] [echo] -------------------------------------------------------------- [echo] [echo] Using Apache Ant version 1.6alpha compiled on April 15 2003 [echo] Build file /home/rubys/jakarta/xml-forrest/build.xml [echo] Build system home ${ant.home} [echo] Build number 0 [echo] Project Name Forrest build file [echo] Java Version 1.4 [echo] Timestamp 200304150151 [echo] [echo] -------------------------------------------------------------- [echo] [mkdir] Created dir: /home/rubys/jakarta/xml-forrest/build validate-config: [echo] validating **/skinconf.xml ... [echo] validating stylesheets **/*.xsl ... [echo] validating **/sitemap.xmap ... fresh-site-zip: [zip] Building zip: /home/rubys/jakarta/xml-forrest/build/fresh-site.zip scratchpad.compile: [mkdir] Created dir: /home/rubys/jakarta/xml-forrest/build/scratchpad/classes [javac] Compiling 37 source files to /home/rubys/jakarta/xml-forrest/build/scratchpad/classes [javac] /home/rubys/jakarta/xml-forrest/src/scratchpad/src/java/org/apache/forrest/components/generator/XNIConfigurableFileGenerator.java:107: org.apache.forrest.components.generator.XNIConfigurableFileGenerator should be declared abstract; it does not define getKey() in org.apache.forrest.components.generator.XNIConfigurableFileGenerator [javac] public class XNIConfigurableFileGenerator [javac] ^ [javac] /home/rubys/jakarta/xml-forrest/src/scratchpad/src/java/org/apache/forrest/yer/use/cocoon/HierarchyGenerator.java:82: org.apache.forrest.yer.use.cocoon.HierarchyGenerator should be declared abstract; it does not define getKey() in org.apache.forrest.yer.use.cocoon.HierarchyGenerator [javac] public class HierarchyGenerator [javac] ^ [javac] 2 errors BUILD FAILED /home/rubys/jakarta/xml-forrest/build.xml:524: Compile failed; see the compiler error output for details. Total time: 11 seconds -- Marc Portier http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://radio.weblogs.com/0116284/ mpo@outerthought.org mpo@apache.org