Re: temporarily disable nags for Directory in gump?
On 8/15/05, Leo Simons [EMAIL PROTECTED] wrote: Would you like access? If you trust me to poke around without damaging anything when a project goes down, I'm happy to go in and fix it again - sure. Heck, would you like to be on the Gump PMC? I have to admit my interests lay with getting projects to play together more than the implementation of gump itself, so I'm not sure I could do that justice :) (also not sure if you are serious :) [EMAIL PROTECTED]:/usr/local/gump/public/workspace/directory-naming$ svn cleanup svn: '' is not a working copy directory Could you be more specific? I was just going off of: http://vmgump.apache.org/gump/public/apacheds/gump_work/update_apacheds.html naming is fine, but appears to be under a cvs subdirectory of workspace: http://vmgump.apache.org/gump/public/gump_repo/gump_work/update_directory-naming.html If that's what you really want. Just comment out the nag/ elements in the descriptors and no e-mail will be sent. Ok, we can discuss that at greater length on directory-dev. I just wanted to get your opinion on the matter. I'll point out that in general if your build keeps breaking (rather than being broken all the time) that's because it keeps changing in non-compatible ways. I know I've always have had loads of trouble getting it all to compile everytime I tried to look at it. Directory does have a problem there. Agreed - that should settle as the individual parts stabilise. But as they chase each others development it will be a problem without a monolithic build. Again, I might put this to the list as a separate item. There is an additional problem in having to maintain two descriptors, which seems to be where a lot of the breakages come from. The addition of dependencies is often needing to be hunted down and added to gump. That could also be viewed as a good thing to take addition of dependencies more seriously, but a hassle when its already been well considered. I guess the thing about it is that even if it isn't a big deal, it is annoying that a perfectly legitimate build will break under gump. Oh, and the second bit I'll mention is that it seems no-one ever pays attention to the builds for their project unless they get e-mail, so there'll probably be a 'hump' to get over once you get back to sending yourself e-mail :-) So densensitized to warning mails now, that I think that's an issue either way :) There's a few example of bigger maven-based builds (for example I know about Excalibur) that tend to build fine. Yep, I don't think there is anything wrong with the Maven support. Mind you -- that's still going to be a while. for gump3, sure - but hopefully some other projects will find directory stuff useful soon. I've already seen talk of MINA on the incubator list today... Thanks for your feedback Leo. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: temporarily disable nags for Directory in gump?
On Monday 15 August 2005 14:13, Brett Porter wrote: Would you like access? If you trust me to poke around without damaging anything when a project goes down, I'm happy to go in and fix it again - sure. They trusted me, so you'll be Ok :o) Heck, would you like to be on the Gump PMC? I have to admit my interests lay with getting projects to play together more than the implementation of gump itself, so I'm not sure I could do that justice :) Brett seems to fit my profile and since I stopped due to lost the morale when the huge success percentage drop occurred, I am sure he will be a great addition to the team. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 11 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Project dnsjava (in module james-server) failed [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Module db-derby success, but with warnings. [EMAIL PROTECTED]: Project jaxen (in module jaxen) failed [EMAIL PROTECTED]: Project commons-jci (in module jakarta-commons-sandbox) failed [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project xml-security-tests (in module xml-security) failed [EMAIL PROTECTED]: Project groovy (in module groovy) failed [EMAIL PROTECTED]: Project commons-feedparser (in module jakarta-commons) failed [EMAIL PROTECTED]: Project derby (in module db-derby) failed [EMAIL PROTECTED]: Module myfaces success, but with warnings. *** G U M P [EMAIL PROTECTED]: Project dnsjava (in module james-server) failed To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project dnsjava has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 26 runs. The current state of this project is 'Failed', with reason 'Missing Build Outputs'. For reference only, the following projects are affected by this: - dnsjava : An implementation of DNS in Java - james-server : James Server Full details are available at: http://vmgump.apache.org/gump/public/james-server/dnsjava/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [dnsjava-1.6.2.jar] identifier set to project name -INFO- Failed with reason missing build outputs -ERROR- Missing Output: /usr/local/gump/public/workspace/james-server/lib/dnsjava-1.6.2.jar -ERROR- See Directory Listing Work for Missing Outputs -DEBUG- Extracted fallback artifacts from Gump Repository To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/james-server/dnsjava/rss.xml - Atom: http://vmgump.apache.org/gump/public/james-server/dnsjava/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3115082005, vmgump.apache.org:vmgump-public:3115082005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project txt2html-task contains errors. The current state of this project is 'Success'. Full details are available at: http://vmgump.apache.org/gump/public/jakarta-servletapi-5/txt2html-task/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole output [ant] identifier set to project name -INFO- Made directory [/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/build/ant] -INFO- No license on redistributable project with outputs. -ERROR- Failed to publish [/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152/build/ant] to repository : [Errno 21] Is a directory The following work was performed: http://vmgump.apache.org/gump/public/jakarta-servletapi-5/txt2html-task/gump_work/build_jakarta-servletapi-5_txt2html-task.html Work Name: build_jakarta-servletapi-5_txt2html-task (Type: Build) Work ended in a state of : Success Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only ant [Working Directory: /usr/local/gump/public/workspace/jakarta-servletapi-5/jsr152] CLASSPATH:
Re: BATCH: All dressed up, with nowhere to go...
On 8/15/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Dear Gumpmeisters, The following 11 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module db-derby success, but with warnings. *** G U M P snip Work ended in a state of : Failed Elapsed: 6 secs Command Line: svn --quiet update --non-interactive db-derby [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: Cannot replace a directory from within This is due to Derby's recent graduation and move out of the incubator, along with its source tree, to live in the db part of the repository. I've attached a patch which updates the URLs (and adds repository/db-svn.xml), but I think someone is going to have to go to where the source is checked out on vmgump and 'svn switch' the source to the new URL. I think there may still be an error to deal with past that, but at least the source will resume updating properly. Thanks, andrew A repository\db-svn.xml M project\db-derby.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
