Hello Luca, Friday, July 18, 2003, 2:16:01 PM, you wrote:
>> -----Original Message----- >> From: Peter Velychko [mailto:[EMAIL PROTECTED] >> Sent: Friday, July 18, 2003 1:03 PM >> To: Stephan Michels >> Subject: Re: cocoon build system >> >> >> Hello Stephan, >> >> Friday, July 18, 2003, 1:25:36 PM, you wrote: >> >> Another problem. >> My classes have the package name beginning not with "org.*" >> But building temporary file "blocks-build.xml" contains in the target >> <target ... name="fins-compile"> the following instruction: >> >> <jar jarfile="${build.blocks}/fins-block.jar"> >> <fileset dir="${build.blocks}/fins/dest"> >> <include name="org/**"/> >> <include name="META-INF/**"/> >> </fileset> >> </jar> >> where "fins" is the name of my block. >> >> So the resulting jar is empty. >> LM> try substituting the jar element with: LM> <jar LM> jarfile="{string('${build.blocks}')}/{$block-name}-block.jar" LM> basedir="{string('${build.blocks}')}/{$block-name}/dest"/> I done the same with a little another way (in my previous mail). I used the value of "/module/project/package" element. LM> Regards, LM> P.S. LM> BTW, I presume you're in the process of packaging the chart-making Cocoon-add-on called "fins" into a block, well... we've just done LM> it ! Yes. It was for "fins". In any case it was the great experience for me. LM> In a few days we'll release the new version of fins as a Cocoon block (thanks to Daniel Fagerstrom for his guidance on Cocoon LM> blocks). It's very nice. Thank you. I'm awaiting your new release. LM> ------------------------------------------ LM> Luca Morandini LM> GIS Consultant LM> [EMAIL PROTECTED] LM> http://space.virgilio.it/kumora/index.html LM> ------------------------------------------ >> >> >> >> I han't found any means to add "third part" jars to >> >> >> {$my_block}.classpath for block sources compiling. >> >> >> >> >> >> Does the possibility exist? >> >> >> >> SM> local.build.properties: >> >> SM> validate.jars=false >> >> >> >> SM> Stephan. >> >> >> >> Thank you. That's really simple :-). >> >> >> >> What is the global reason to validate "jar"-libraries? >> >> SM> To validate name of the jars, and if there exist >> SM> a description from where the lib comes, where it is >> SM> used. >> >> SM> We have approximately 100 jars, this target helps to >> SM> get the overview. >> >> >> Also I added the new element "dependjar" for "project" into the >> >> "gump.xml" and changed "blocks-build.xsl" to process the added >> >> element and it work also. >> >> SM> Fine :) >> >> SM> Have fun, Stephan. >> >> >> SM> --------------------------------------------------------------------- >> SM> To unsubscribe, e-mail: [EMAIL PROTECTED] >> SM> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> -- >> Best regards, >> Peter Velychko >> [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> LM> --------------------------------------------------------------------- LM> To unsubscribe, e-mail: [EMAIL PROTECTED] LM> For additional commands, e-mail: [EMAIL PROTECTED] -- Best regards, Peter Velychko [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
