Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 56566 invoked by uid 500); 22 Jun 2001 08:51:42 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 56554 invoked from network); 22 Jun 2001 08:51:42 -0000 From: "Carsten Ziegeler" To: Subject: AW: [C2] Build targets Date: Fri, 22 Jun 2001 10:42:57 +0200 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <993115464.3b31bd48798f2@mail.otego.com> Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.5 |September 22, 2000) at 22.06.2001 10:42:36, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.5 |September 22, 2000) at 22.06.2001 10:51:12, Serialize complete at 22.06.2001 10:51:12 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > Giacomo Pati wrote: > > Quoting Carsten Ziegeler : > > > > Konstantin Piroumian wrote: > > > > > > > > Hi, Cocooners! > > > > > > > > > > Is there a way to build C2 without samples and unnecesary > > libraries? > > > > > > > > Yes, delete them ;). > > > > > > How can I know which jar is necessary for Cocoon engine and which one > > is > > > used only in a sample? Of course, I can try to delete one-by-one and > > see > > > what happens :) > > > > > > > > > > > > I need to get a clear cocoon.war - without specific Actions, jars > > and > > > > > samples. > > > > > > > > Well, this is a matter of taste and I don't see a general way to > > specify > > > > which jars are not needed. the samples are in the webapp subdiretory > > > > which is easily deletable. > > > > > > As I can see, this jars are not necessary if I don't need samples and > > some > > > of the actions: > > > > > > axis.jar > > > axis-samples.jar > > > batik-libs.jar > > > bsf.jar > > > fop-0_18_1.jar > > > hsqldb.jar > > > jimi-1.0.jar > > > junit.jar > > > maybeupload.jar > > > rhino.jar > > > Tidy.jar > > > velocity-1.1-rc1.jar > > > xt.jar > > > > > > Am I right or maybe some this libs is required for Cocoon itself? > > > > > Am not sure about all of them but the maybeupload.jar is required as it > > is > > directly used by the Request object created for each request. > > All others seem to be optional, but of course you have to remove all > > references > > from the sitemap.xmap, e.g. you have to remove the html generator etc. > > > > > > > > > > > Just the core of Cocoon, so I could add my application files, > > > > > classes, jars and sitemaps and create a war for my application > > only. > > > > > > > > I don't see what the "core Cocoon" is. > > > > > > By "core Cocoon" I mean Cocoon engine without any Form > > > processing, DB, SVG, > > > FOP, i18n samples and actions. > > > > > > But... maybe you are right saying that it's easier to delete all > > > unnecessary > > > things that you don't need in your application. > > > > > Personally, I don't like the term "core Cocoon" for this case as I > > think that the "core Cocoon" is the whole project without examples. > > But this includes all provided generators, transformers etc. as most > > of them are very usefull and also required to build web applications. > > What you think of, I would rather call a "minimal Cocoon". > > But anyway these are only terms. > > One thing that we can do for convenience is to update the build.xml to not > depend on specific jars and exclude the sources for compilation > if those jars > are absent (see PhpGenerator). > Hi, I just added a very simple command line tool (called st for sitemap tool) which is actually a java class. This tool can be called from the build.xml during build and can add sitemap entries to the build sitemap.xmap. I changed the build.xml so that an entry for the PhpGenerator is added to the sitemap if the php generator is compiled. We could do this for all other "optional" components as well, for example even for the fop classes. So we would need to add more complexity to the build script. One could also imagine to add a new constraint saying: "examples or not" and we could enhance the st tool to generate (include) example pipelines during the build rather then hardcoding in the build.xml. Carsten Open Source Group sunShine - b:Integrated ================================================================ Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn www.sundn.de mailto: cziegeler@sundn.de ================================================================ > Giacomo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org