Re: Newsletter - Request for content
As you can see the timetable has slipped a bit! However, there doesn't seem to be a lot to go in this issue (just an entry for lucene + whatever I write to summarise general@) and I was wondering whether it was worth bothering with. I realise this is to be expected with the Christmas / New Year but there has been a general decline in content volume over the months and I was wondering whether there was something that should be done to address this. A number of thoughts have been mentioned by various people and I'd be interested to hear opinions: Reduce the frequency - every 2 months has been suggested before. Format revamp - no idea how but ideas welcome - perhaps new blood is required? Widen the scope - ant and Avalon have grown up to be (at least partially) outside the jakarta scope, should we include xml.apache.org? and it's children? maybe just a simple *.apache.org? (with some appropriate rename) Maybe its fine as it is? Thanks, Rob - Original Message - From: Rob Oxspring [EMAIL PROTECTED] To: 'Jakarta General List' [EMAIL PROTECTED] Cc: 'James Strachan' [EMAIL PROTECTED]; 'Henri Yandell' [EMAIL PROTECTED]; 'Conor MacNeill' [EMAIL PROTECTED]; 'Stefan Bodewig' [EMAIL PROTECTED]; 'Otis Gospodnetic' [EMAIL PROTECTED]; 'David Sean Taylor' [EMAIL PROTECTED]; 'Martin Poeschl' [EMAIL PROTECTED] Sent: Sunday, December 29, 2002 2:30 PM Subject: Newsletter - Request for content The end of the month is approaching again and I'm sure that, like me, a lot of you are focused on celebrating the new year. Once all that is over I'd like to post the December issue of the newsletter so if people can send any reports to me that would be great. Everyone is welcome to send summaries of any jakarta issues, those CC'd are so since they posted last time and are asked for a repeat effort or to try and prod others on the respective lists into taking over. In terms of timescale I'd like to pull the drafts together next weekend and post as soon as additions stop trickling in. If the timescale doesn't suit but you'd like to contribute then give me an idea of you'll have something ready and we can discuss how long we can wait. In the meantime, thanks everyone and Happy New Year! Rob P.S. Big thanks to Otis for beating the content request! As usual! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Newsletter - Request for content
Rob Oxspring wrote: Reduce the frequency - every 2 months has been suggested before. If you have the energy, 1 month is nice. PArtecipating is not compulsory, so some projects may do it with less frequency. Format revamp - no idea how but ideas welcome - perhaps new blood is required? I like the format :-) Widen the scope - ant and Avalon have grown up to be (at least partially) outside the jakarta scope, should we include xml.apache.org? and it's children? maybe just a simple *.apache.org? (with some appropriate rename) If you have energy to bring in the xml.apache projects it would be great! Then others too, but maybe one step at a time could help. Maybe its fine as it is? Your work is very much appreciated :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Newsletter - Request for content
On Wed, Jan 08, 2003 at 12:46:25PM -, Rob Oxspring wrote: As you can see the timetable has slipped a bit! However, there doesn't seem to be a lot to go in this issue (just an entry for lucene + whatever I write to summarise general@) and I was wondering whether it was worth bothering with. I realise this is to be expected with the Christmas / New Year but there has been a general decline in content volume over the months and I was wondering whether there was something that should be done to address this. A number of thoughts have been mentioned by various people and I'd be interested to hear opinions: Reduce the frequency - every 2 months has been suggested before. Format revamp - no idea how but ideas welcome - perhaps new blood is required? How about setting up an 'ApacheNewsletter' Wiki page, let content accumulate, and publish once critical mass is achieved? I'd imagine that writing a newsletter entry is no fun at all. Probably each project has only 2 or 3 people with a broad enough understanding of the issues to 'summarize' a month's communications, identifying the signal amongst the noise. It's also a rather subjective task, with a high risk of offending someone by omitting or misrepresenting points. Using a Wiki doesn't solve the hard problems, but does lower the barrier to entry, and makes plain that it's everyone's problem to create content, not just the dedicated few listed below. Widen the scope - ant and Avalon have grown up to be (at least partially) outside the jakarta scope, should we include xml.apache.org? and it's children? maybe just a simple *.apache.org? I know Forrest has a willing contributor :) and I'm sure with some arm-twisting, one could be found for Cocoon. --Jeff (with some appropriate rename) Maybe its fine as it is? Thanks, Rob - Original Message - From: Rob Oxspring [EMAIL PROTECTED] To: 'Jakarta General List' [EMAIL PROTECTED] Cc: 'James Strachan' [EMAIL PROTECTED]; 'Henri Yandell' [EMAIL PROTECTED]; 'Conor MacNeill' [EMAIL PROTECTED]; 'Stefan Bodewig' [EMAIL PROTECTED]; 'Otis Gospodnetic' [EMAIL PROTECTED]; 'David Sean Taylor' [EMAIL PROTECTED]; 'Martin Poeschl' [EMAIL PROTECTED] Sent: Sunday, December 29, 2002 2:30 PM Subject: Newsletter - Request for content ... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Help needed on JMeter nightly builds
Hi all. Hi Sam. So it was YOU who repaired the JMeter build on the 2nd Jan! I was about to go mad. Anyway, thanks. I think I get the picture now. Would you (or someone else) be so kind as reviewing this for severe misunderstandings? * Gump reads the project descriptors to establish a dependency tree, then builds each project in order. * Gump uses a modified ant which totally ignores all classpath settings -- instead it places all JARs exported by projects depended upon into the classpath. Q1: is it then best practice to remove all those jars from our lib/*.jar in CVS? * Thus the Gump nightly builds always happen against the CVS versions of all projects -- which means that if I build JMeter from the sources on my workstation I won't get the exact same results (since I will be building against released versions of those projects). * The copying of build results to http://cvs.apache.org/builds/jakarta-jmeter/nightly/ is not done by Gump. (Even though it must be run just after (some?) builds). Q: how can I have the JMeter distribution files published there? * The publishing of the src snapshot in that same directory has nothing to do with Gump. Salut, Jordi. Sam Ruby wrote: Jordi Salvat i Alabart wrote: Hi Sam. I'm taking this out of general to avoid bugging everyone around with my stupidness. Don't be afraid to post e-mails like these on jakarta-general. That way everybody can help, and everyone can learn from the answers. First of all, thanks again for your help, and my apologies if you just don't have time to help newcomers. I do get a lot of e-mails, so I may occasionally miss one. If that happens, try again. Or, ask on general. I have many questions about the nightly build snapshot process, how it names the results and where it places them. Every project in Jakarta seems to work in a slightly different way -- and JMeter most different of all. I also have questions on how the web site is generated and published (I'd like JMeter's to be generated from the xdocs instead of just pulled out from cvs/jakarta-jmeter/docs). There are some general policies, and then each subproject in Jakarta is free to tailor them to their own needs. The nightly build simply checks out jakarta-jmeter and builds the default target. It is driven from the following project definition: http://cvs.apache.org/viewcvs/jakarta-gump/project/jakarta-jmeter.xml I am willing to upload to the jakarta web site anything that build produces, simply ask. The way most jakarta projects work, as does jmeter, is that there is a docs target in the build that generates the docs directory from the xdocs sources. Simply build this and then commit the generated docs. Then somebody needs to go onto the daedalus.apache.org and execute a cvs update to get resynch the website with the cvs tree. For a number of projects, I have a script that automatically does this four times a day, so this eliminates a step... all you need to do is build and commit. Jmeter is not currently in this script... but can be added upon request. I've been checking the FAQ at http://www.apache.org/dev/committers.html#web, but it didn't help much. Either it's obsolete, or it doesn't apply to all jakarta projects. Is there any documentation I could read to get better informed? Most of the jakarta documentation is on jakarta.apache.org. Try clicking on gump or Website Maintenance. - Sam Ruby -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Help needed on JMeter nightly builds
Jordi Salvat i Alabart wrote: * Gump reads the project descriptors to establish a dependency tree, then builds each project in order. Yes. * Gump uses a modified ant which totally ignores all classpath settings -- instead it places all JARs exported by projects depended upon into the classpath. Ant isn't modified, it is passed a build.sysclasspath paramter. The version of Ant which is used to do the builds is built from cvs. But, effectively, the result is the same. Q1: is it then best practice to remove all those jars from our lib/*.jar in CVS? While removing such jars is my preference, others will disagree. Suffice it to say that there is no consensus. * Thus the Gump nightly builds always happen against the CVS versions of all projects -- which means that if I build JMeter from the sources on my workstation I won't get the exact same results (since I will be building against released versions of those projects). True. You also won't get the exact same results if you use a different compiler. ;-) * The copying of build results to http://cvs.apache.org/builds/jakarta-jmeter/nightly/ is not done by Gump. (Even though it must be run just after (some?) builds). Q: how can I have the JMeter distribution files published there? As you have an id on that machine, you are certainly welcome to publish files there. The SCP utility is handy for such things. Also, anything that I build with gump that you find of value, I am willing to upload. You will find that a lot of things work this way around here. While you will occasionally find somebody telling you what *not* to do, and often find that there are people who will tell you what they are willing to do, you will rarely find somebody telling you what to do. In this case: if you want me to upload more, fine. If you want me to upload less, fine. Just don't ask me to build something different. * The publishing of the src snapshot in that same directory has nothing to do with Gump. gump starts out by doing a cvs update directory maintained separate from the build. At the end of the gump run, that directory is zipped and tarred up and uploaded. - Sam Ruby -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
