Re: [GUMP][PATCH] cocoon seems to require log4j
Adam R. B. Jack wrote: Folks, Could somebody take time to apply Stefan's patch? It would be awesome to see the Cocoon branch of things start to be built by Gump (now that it finally can). Thanks in advance. Sorry, we were in the middle of switching to use SVN. Patches applied now to depend logging-log4j and to enable Gump to use our new SVN trunk. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrestbot on brutus
Leo Simons wrote: Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. please understand that brutus is untrusted. We shouldn't have brutus autopublish results to ASF websites (which would mean an SSH connection from brutus to minotaur, which wouldn't be nice). other than that, no problems. Just list what you need...I'd prefer to just create an account and webspace and have the forrest guys manage the forrest bot... (Hi all, i just joined generalATgump ... been meaning to do so for ages. We had talked in the past about helping Gump with a Forrest webapp for other purposes.) Leo, we had an excellent discussion on infra@ about ASF publishing of websites (see forrestbot thread). There were good outcomes. We do *not* want to publish anything from brutus to minotaur. The infrastructure discussion suggested that we cooperate with Gump and use brutus to conduct an experimental install of the forrestbot webapp interface and of the forrestbot production system. Later there would be a trusted machine where we could run an ASF forrestbot. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help please: how to maintain project descriptor
The Gump build of Forrest has been failing lately, but i don't have a clue what is wrong and why it suddenly started doing this. Is there a description somewhere of how to write a project.xml for gump? Ours is old and might need tweaking. Are there some recommended examples to follow? Anyway, here is our current issue: -ERROR- Bad Dependency. Project: ant-contrib unknown to *this* workspace -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help please: how to maintain project descriptor
Adam R. B. Jack wrote: David Crossley wrote: Is there a description somewhere of how to write a project.xml for gump? Ours is old and might need tweaking. Are there some recommended examples to follow? http://gump.apache.org/metadata/index.html Du'oh thanks. I thought that i had wandered all around the website looking for that, but didn't think to go to the Object Model tab. As penance, i added an entry to the FAQ. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [GUMP@brutus]: cocoon-2.1/cocoon failed
Done, thanks. --David Stephen McConnell wrote: I'm in the process of updating a bunch of Avalon related gump descriptors to reference current content in svn (as opposed to cvs content). Part of the transition also involves linking gump build procedures with magic based builds and getting this all in sync means a couple of changes on dependent projects. One of these concerns the avalon-framework references. Could someone please update the cocoon-2.1/cocoon gump descriptor and replace the following line: depend project=avalon-framework ids=impl api / with: depend project=avalon-framework-api/ depend project=avalon-framework-legacy/ depend project=avalon-framework-impl/ Steve. -Original Message- From: Gump [mailto:[EMAIL PROTECTED] Sent: 22 August 2004 09:10 To: [EMAIL PROTECTED] Subject: [EMAIL PROTECTED]: cocoon-2.1/cocoon 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 folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 1 projects. Project State : 'Failed', Reason 'Configuration Failed' The following are affected: - cocoon : Java XML Framework Full details are available at: http://brutus.apache.org/gump/public/cocoon-2.1/cocoon/index.html That said, some snippets follow: The following annotations were provided: -DEBUG- Jar [cocoon.jar] identifier set to jar basename: [cocoon] -DEBUG- Jar [cocoon-tests.jar] identifier set to jar basename: [cocoon- tests] -DEBUG- Jar [cocoon-deprecated.jar] identifier set to jar basename: [cocoon-deprecated] -ERROR- No such project [avalon-framework] for property. -ERROR- Cannot resolve jar/jarpath of *unknown* [avalon-framework] -ERROR- Unhandled Property: avalonapi.jar on: Ant on Project:cocoon -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: avalon-framework unknown to *this* workspace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Ant-contrib-developers] [GUMP@brutus]: ant-contrib/ant-contr ib failed
Adam R. B. Jack wrote: I am looking into the problem now. It looks like bleed in from another project, who (due to some complexities of gump) were able to write into your project. I've found the cause, see bottom of: http://svn.apache.org/repos/asf/forrest/trunk/module.xml I also wasn't clear here. Could you forret folk not have a project called ant-contrib in your module descriptor, or (at least) call it something local. BTW: Why can't you use the CVS HEAD one? Fixed, sorry about that. It was a relic of someone trying to fix things when we got failures of ant-contrib due to sf not being available recently. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cannot reach Nightlies from home page
Is the link in the left-panel Nightlies pointing to an old server or is gump.covalent.net down? -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] fixing gump
Adam R. B. Jack wrote: A tweet from the background ... Very welcome. The email reports that nag us on Cocoon and Forrest are very hard for me to follow. (Please don't stop the nags.) I do try to decipher them and even follow through to the website. However, i inevitably give up and wait. Bummer. Can you point to parts that are confusing? I'd appreciate any feedback on wording, or content, or format, or whatever. Looking at the following messages seems to say that we stuffed up our descriptor about ant-contrib. http://marc.theaimsgroup.com/?t=10971205321 snip The following annotations were provided: -INFO- Failed with reason configuration failed -ERROR- Bad Dependency. Project: ant-contrib unknown to *this* workspace -INFO- Failed to extract fallback artifacts from Gump Repository /snip For the second time, one of our committers jumped in to define it in our descriptor, which we had to revert. You had told us before that it was not actually our problem. That was the only reason that i knew what to do, i.e. wait. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: building Forrest (Was: [RT] fixing gump)
Niclas Hedhman wrote: David Crossley wrote: It seems that Gump is still using the old descriptor in our SVN. How do i get Gump to switch? The profile/gump.xml looks okay, but the last time that it was built was two days ago using the old descriptor. It doesn't look Ok in my checked out copy. Have you perhaps forgotten to commit it? Anyway, I have committed the change I think is necessary... Ah i see. Stefano moved Forrest and Lenya descriptors but disabled Forrest. I am beginning to understand the configuration. Thanks everyone. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [rant] I hate this gump
Scott Sanders wrote: Stefano Mazzocchi wrote: and you can bet your ass that the webapp will *NOT* be written in python. ooh, ooh, is it ruby? :-P it's going to be the simplest thing (for me!) that can possibly work. which is probably going to be cocoon ;-) That's a HUGE hammer, I hope you're pounding some big nails :) Scott What happened to the middle of this thread? Did it go off-list for a while? -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RT] fixing gump
Stefano Mazzocchi wrote: Adam R. B. Jack wrote: snip/ Cocoon didn't build 'cos (1) we'd not got enough folks caring about gump successes (2) we didn't build from repository (and cocoon has lots of dependencies, so it's chances of a build were unlikely. FWIIW: Communities (many), along with myself (looking at 'affected') and Stefan (just being the natural Gumpmeister) put in the time and effort in to picked candidate failures, fix them, and slowly edged up the Gump wave front to meet Cocoon. So, in a sense, this number resulted in Cocoon getting built. ;-) all right, it is clearly not your fault that cocoon was never built, but this for sure didn't help, IMHO. A tweet from the background ... The email reports that nag us on Cocoon and Forrest are very hard for me to follow. (Please don't stop the nags.) I do try to decipher them and even follow through to the website. However, i inevitably give up and wait. Thank heaven that Stefan Bodewig and Stephen McConnell et al sometimes send us a fix for our gump descriptor. These fixes are often obscure. So, please, it is not that we don't care. How to ease the confusion, i do not know. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] move the descriptors in our hands
Stefano Mazzocchi wrote: There are 4 ASF descriptos that currently don't reside in our repository: 1) avalon_trunk 2) cocoon 3) forrest 4) lenya and a few others (3) from outside. I would strongly suggest that we start moving them. The only problematic one is cocoon's since it's a central piece of the build system. But this can be easily solved with svn:external if we move the metadata in SVN. At Forrest our module.xml is an integral part of our build. I gather that we could use the svn:externals property too. We could instead re-structure our build system at Forrest to not depend on the module.xml file. At first glance it is just to grab our version number. However, we are just about to enter a release process, so not yet. Anyway, +1 from me (still need to raise on forrest-dev) for moving our metadata to the Gump repository and +1 for moving all Gump metadata to SVN. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] move the descriptors in our hands
Stefano Mazzocchi wrote: David Crossley wrote: At Forrest our module.xml is an integral part of our build. I gather that we could use the svn:externals property too. yes, if that's the need, yes. note however, how svn:external works only on a folder (or, at least, I couldn't make it work on a single file) Drat, no good then, because we only want the one file. an alternative, which I'm considering for cocoon too, is to use a get operation in the build.xml that fetches the file directly from the CVS repository via viewCVS. This would allow us to avoid moving the metadata to SVN entirely! Sounds good. We could instead re-structure our build system at Forrest to not depend on the module.xml file. At first glance it is just to grab our version number. However, we are just about to enter a release process, so not yet. hmmm, if it's just the version number, it's a trivial change, as you can place that into the build.properties files and be as happy. Yes. We do not have build.properties, but can do something. in any case, it is failing so I will start moving it over anyway. you guys can decide what to do on your own. As far as i can tell, it is failing because ant-contrib is failing and we get some previous build of that. Not our failure, so i didn't do anything. We have had this one before. Anyway, +1 from me (still need to raise on forrest-dev) please do for moving our metadata to the Gump repository and +1 for moving all Gump metadata to SVN. with the above get trick it might not be necessary for now. Will investigate. As i said we are not doing any change for now, due to imminent release. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
failure of ant-contrib busts Forrest (Was: [vote] move the descriptors in our hands)
Stefano Mazzocchi wrote: David Crossley wrote: As far as i can tell, it is failing because ant-contrib is failing and we get some previous build of that. Not our failure, so i didn't do anything. We have had this one before. no, it's not because ant-contrib is failing, but because it's no longer there! where did ant-contrib go btw? It is not ant as in Apache Ant. It is a SourceForge project. Last time this happened it was because SF.net was failing or their CVS or something, IIRC. Last time, we mistakenly tried to add an entry to our Gump descriptor, thinking that we were missing something. Adam stepped in and found the cause and asked us to remove it. So i suppose it is defined elsewhere. I am lost sorry. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] move metadata to SVN
Stefano Mazzocchi wrote: I propose to move the gump metadata over to SVN and close down the CVS repository. +1 -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
Niclas Hedhman wrote: Stefan Bodewig wrote: Niclas Hedman wrote: Adding the xmlParserAPIs for some Maven projects in Fulcrum. + project name=xmlParserAPIspackage=jetty-5.0.RC4/ Isn't this the same jar that we created during the Xerces build? The 2.5 in the jar name in Jetty suggests Xerces-J 2.5 to me. Perhaps. Feel free to try to get the name xmlParserAPIs to map against the Maven artifactID of the same name. ATM, type=boot jars will not map to Maven jar overrides, and I couldn't figure out any other way to handle this. Is this the same xml-apis that are provided by Apache XML Commons? -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
Stefan Bodewig wrote: Dion Gillard wrote: The xmlParserAPIs is from memory a rename of xml-apis from xml-commons, provided by xerces in it's download, right? Yes and no. The version shipped by Xerces is far more advanced than the latest released version (and even that has been a beta) of xml-commons. Ant 1.6.x ships the Xerces version because of that, for example. Wow, i always did worry that that might be the case. I understood that xml-commons was supposed to be the official home. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: I understood that xml-commons was supposed to be the official home. So do I. When we prepared the release of Ant 1.6.0 we realized that Xerces wouldn't work with the 1.0beta2 release from xml-commons, so we were forced to do something about it. We ship the Xerces version until xml-commons comes up with a release (which we asked for a couple of times). However it is XML Commons. All XML committers have commit access, so that they can do it there. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project xml-apis.xml
Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: I understood that xml-commons was supposed to be the official home. So do I. When we prepared the release of Ant 1.6.0 we realized that Xerces wouldn't work with the 1.0beta2 release from xml-commons, so we were forced to do something about it. We ship the Xerces version until xml-commons comes up with a release (which we asked for a couple of times). However it is XML Commons. All XML committers have commit access, so that they can do it there. I think you are not critizing me or the Ant folks (the we in my statements), but I want to make that clear. That is correct, not criticising you or Ant. Actually criticising (hopefully constructively) the situation that can allow this to happen. Of course I'd think that Xerces would ship a released version of xml-commons instead of a home-brewed. Since they did not and since there still hasn't been a new release of the xml-apis today, Ant was forced to ship what we had. That is the problem. The Xerces people have commit rights to xml-commons. I get hot under the collar when people criticise a project from afar, yet it is within their power to help to do something about it. By the way, if any Ant committers want to help the poor neglected XML Commons project, then come on over. There is a new/updated version of JAXP due to come to Apache XML soon. Let us hope that it lands in the right place. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrest.xml doesn't validate
Leo Simons wrote:
Hi gang,
./validate says today:
This did used to validate recently. I see from the
commit history that various people have since been
making changes but not using the 'validate' script.
I just moved the basedir attribute from the project
elements to the ant elements. Not sure if that is correct.
Would someone please help us to sort out the mess.
--David
Processing Local Projects
./tmp/./project/forrest.xml:33: element project: validity error : No
declaration for attribute basedir of element project
project name=forrest basedir=main
^
./tmp/./project/forrest.xml:62: element project: validity error : No
declaration for attribute basedir of element project
project name=forrest-forrestbar basedir=tools/forrestbar
^
./tmp/./project/forrest.xml:73: element project: validity error : No
declaration for attribute basedir of element project
project name=forrest-whiteboard-forrestdoc
basedir=whiteboard/forrestdoc
^
./tmp/./project/forrest.xml:89: element project: validity error : No
declaration for attribute basedir of element project
ct name=forrest-whiteboard-forrestdoc-autotest
basedir=whiteboard/forrestdoc
^
---
Now, I have no real idea what validate is or how it works, but this is
probably a bad thing...
cheers,
- Leo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrest.xml doesn't validate
On Wed, 2004-11-10 at 11:36, David Crossley wrote: Leo Simons wrote: Hi gang, ./validate says today: This did used to validate recently. I see from the commit history that various people have since been making changes but not using the 'validate' script. I just moved the basedir attribute from the project elements to the ant elements. Not sure if that is correct. Would someone please help us to sort out the mess. It seems that we now have a successful build of Forrest after making that change above and another actual code change where we were using a deprecated part of Cocoon. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
a gump sucess story (was: [EMAIL PROTECTED]: Project forrest (in module forrest) failed)
Gump wrote: To whom it may engage... Thanks Gump. Please don't stop your notifications. A couple of days ago i changed something in Cocoon that looked like it was concerned only with documentation generation. However it was also the name of the actual component and is used to build the default sitemap. Yeah, i broke it. But i didn't find out about it until Gump failed to build Forrest. Sorry to everyone, thanks to Gump. --David 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 forrest has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - forrest : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://brutus.apache.org/gump/public/forrest/forrest/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/forrest/forrest/gump_work/build_forrest_forrest.html Work Name: build_forrest_forrest (Type: Build) Work ended in a state of : Failed Elapsed: 4 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-xerces2/java/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/java/build/xalan-unbundled.jar:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=01122004 gump [Working Directory: /usr/local/gump/public/workspace/forrest/main] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/forrest/build/components/classes:/usr/local/gump/public/workspace/forrest/build/scratchpad/classes:/usr/local/gump/public/workspace/ant/dist/lib/ant-stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/build/lib/ant-contrib-01122004.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-01122004/cocoon.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-01122004/cocoon-testcase.jar:/usr/local/gump/public/workspace/cocoon/build/cocoon-01122004/cocoon-deprecated.jar:/usr/local/gump/publi c/workspace/xml-commons/java/build/resolver.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/api/target/deliverables/jars/avalon-framework-api-01122004.jar:/usr/local/gump/public/workspace/avalon-tools/tools/magic/target/deliverables/jars/avalon-tools-magic-01122004.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/legacy/target/deliverables/jars/avalon-framework-legacy-01122004.jar:/usr/local/gump/public/workspace/avalon-trunk/runtime/framework/impl/target/deliverables/jars/avalon-framework-impl-01122004.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-i18n-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-compatibility-1.1.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-configuration-1.2.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-manager-interfaces-1.0.jar:/usr/local/gump/packages/excalibur-legacy/excalibur-instrument-1.0.jar:/usr/local /gump/packages/excalibur-legacy/excalibur-instrument-manager-1.0.jar:
Re: XML Resolver for Xerces on Kaffe was Re: Hello Gump)
Stefano Mazzocchi wrote: Davanum Srinivas wrote: oops...i updated brutus.xml as ANT_OPTS is not really picked up. Added: sysproperty name=jikes.class.path value=/usr/local/gump/kaffe/workspace/xml-xerces2/java/tools/resolver.jar/ Anybody against removing this and adding a dependency on xml-commons/resolver from xml-xerces2? I wondered from the beginning of this thread if that might be what is needed. I checked the 'cvs log' for that resolver.jar and it is the xml commons version. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrestbot on brutus
I would like to follow up on this now. Sorry i had to leave it sit for a while, but ready to go now. So could we have two accounts to start with: Dave Brondsema [EMAIL PROTECTED] David Crossley [EMAIL PROTECTED] We would like to set up forrest as a webapp under Tomcat and also the forrestbot webapp interface. We would also install forrest on the system for anyone to use as a command-line tool and for use by the forrestbot. We are not yet sure where things should live on the brutus filesystem. --David On 2004-08-03 David Crossley wrote: Leo Simons wrote: Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. please understand that brutus is untrusted. We shouldn't have brutus autopublish results to ASF websites (which would mean an SSH connection from brutus to minotaur, which wouldn't be nice). other than that, no problems. Just list what you need...I'd prefer to just create an account and webspace and have the forrest guys manage the forrest bot... (Hi all, i just joined generalATgump ... been meaning to do so for ages. We had talked in the past about helping Gump with a Forrest webapp for other purposes.) Leo, we had an excellent discussion on infra@ about ASF publishing of websites (see forrestbot thread). There were good outcomes. We do *not* want to publish anything from brutus to minotaur. The infrastructure discussion suggested that we cooperate with Gump and use brutus to conduct an experimental install of the forrestbot webapp interface and of the forrestbot production system. Later there would be a trusted machine where we could run an ASF forrestbot. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
native line-endings (Was: svn commit: r111800 - /gump/trunk/python/gump/core/model/project.py)
Stefan Bodewig wrote: This change looks far bigger than it actually was because of line-end tranformations. I vaguely recall there is a property we should add to the auto-props so that all *.py files are assumed to have platform specific line-feeds by SVN, but I've lost the details right now. * Make sure that the file has the proper line endings for whatever operating system you are on. * svn add myfile.txt * svn propset svn:eol-style native myfile.txt You can configure your svn client to do it automatically. We created a config file at Forrest: http://issues.cocoondev.org/browse/FOR-124 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: Project forrest (in module forrest) failed
Help please. Forrest has been failing for a few days with no clues in the Gump build output. It seems to be failing on the Ant xmlvalidate task. It gets past this in a local build, so that makes me wonder if the ant-apache-resolver and xml-commons-resolver are not available to it on brutus. I tried adding depends for these but that is obviously not correct ... the gump run says ant-apache-resolver not known to this workspace. Do we need to depend on bootstrap-ant instead? We have disabled the use of xmlvalidate from our build to get past this hurdle. (As you can see, i don't know what i am doing. Sorry for bashing away, but someone has gotta try.) I see that there are two names in Gump for the resolver from xml-commons (xml-commons-resolver and xml-resolver). Why two? The XML Commons release calls it xml-commons-resolver. --David David Crossley wrote to forrest-dev: Juan Jose Pablos wrote: validate-config: [echo] validating **/skinconf.xml ... BUILD FAILED /home/gump/workspaces2/public/workspace/forrest/main/build.xml:294: The following error occurred while executing this line: /home/gump/workspaces2/public/workspace/forrest/main/build.xml:162: /home/gump/workspaces2/public/workspace/forrest/main/site not found. Does anyone know why is this happening? I did have a look and I could not find a clue. It is failing on the xmlvalidate task (look at the line numbers in build.xml). Yesterday i changed our Gump descriptor to depend on xml-commons-resolver and ant-apache-resolver ... i was guessing that is the problem. However, i don't see any new message from Gump, either success or fail. I will go to ask for help on [EMAIL PROTECTED] --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: Project forrest (in module forrest) failed
Help please. Forrest has been failing for a few days with no clues in the Gump build output. It seems to be failing on the Ant xmlvalidate task. It gets past this in a local build, so that makes me wonder if the ant-apache-resolver and xml-commons-resolver are not available to it on brutus. I tried adding depends for these but that is obviously not correct ... Kaffe run says ant-apache-resolver not known to this workspace. Do we need to depend on bootstrap-ant instead? (As you can see, i don't know what i am doing. Sorry for bashing away, but someone has gotta try.) I see that there are two names in Gump for the resolver from xml-commons (xml-commons-resolver and xml-resolver). Why two? The XML Commons release calls it xml-commons-resolver. --David David Crossley wrote to forrest-dev: Juan Jose Pablos wrote: validate-config: [echo] validating **/skinconf.xml ... BUILD FAILED /home/gump/workspaces2/public/workspace/forrest/main/build.xml:294: The following error occurred while executing this line: /home/gump/workspaces2/public/workspace/forrest/main/build.xml:162: /home/gump/workspaces2/public/workspace/forrest/main/site not found. Does anyone know why is this happening? I did have a look and I could not find a clue. It is failing on the xmlvalidate task (look at the line numbers in build.xml). Yesterday i changed our Gump descriptor to depend on xml-commons-resolver and ant-apache-resolver ... i was guessing that is the problem. However, i don't see any new message from Gump, either success or fail. I will go to ask for help on [EMAIL PROTECTED] --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: Project forrest (in module forrest) failed
Stefan Bodewig wrote: David Crossley wrote: Help please. Forrest has been failing for a few days with no clues in the Gump build output. It seems to be failing on the Ant xmlvalidate task. It gets past this in a local build, so that makes me wonder if the ant-apache-resolver and xml-commons-resolver are not available to it on brutus. Since you depend on ant which has been compiled without resolver instead of dist-ant. I'll move the resolver dependency to ant since Xerces needs it anyway. You can add back the xmlvalidate step once I'm done (a couple of minutes, I guess). You are a champion. Thanks, it worked. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Gump3 branch
Leo Simons wrote: Pfew. We really should start writing some unit tests. If I had the time I would start from scratch one more time using a test-first approach, but I haven't figured out how to comfortably do test-first python development yet. That paragraph sounds extremely important to this novice. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cvs commit: gump/project ant-contrib.xml forrest.xml
Thanks for looking after us Stefan. I would never have guessed that that was needed to fix the gump of forrest. --David [EMAIL PROTECTED] wrote: bodewig 2005/01/18 00:18:14 Modified:project ant-contrib.xml forrest.xml Log: ant-contrib needs bcel at runtime Revision ChangesPath 1.4 +1 -1 gump/project/ant-contrib.xml Index: ant-contrib.xml === RCS file: /home/cvs/gump/project/ant-contrib.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- ant-contrib.xml 10 Jan 2005 16:16:23 - 1.3 +++ ant-contrib.xml 18 Jan 2005 08:18:14 - 1.4 @@ -32,7 +32,7 @@ depend project=ant inherit=runtime/ depend project=xml-xerces/ -depend project=bcel/ +depend project=bcel runtime=true/ jar name=build/lib/ant-contrib-@@DATE@@.jar / license name=manual/LICENSE.txt/ 1.14 +4 -4 gump/project/forrest.xml Index: forrest.xml === RCS file: /home/cvs/gump/project/forrest.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- forrest.xml 18 Dec 2004 22:38:09 - 1.13 +++ forrest.xml 18 Jan 2005 08:18:14 - 1.14 @@ -1,6 +1,6 @@ ?xml version=1.0? !-- - Copyright 2002-2004 The Apache Software Foundation + Copyright 2002-2005 The Apache Software Foundation Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. @@ -38,7 +38,7 @@ !-- Project jars Forrest build strictly depends on -- !-- needed for build -- depend project=ant/ -depend project=ant-contrib/ +depend project=ant-contrib inherit=runtime/ depend project=xml-xerces/ depend project=xalan/ depend project=cocoon inherit=all/ @@ -76,7 +76,7 @@ work nested=whiteboard/forrestdoc/build/tools/ant/ home nested=whiteboard/forrestdoc/dist/ depend project=ant/ -depend project=ant-contrib/ +depend project=ant-contrib inherit=runtime/ depend project=xml-xerces/ depend project=xalan/ depend project=antlr/ @@ -90,7 +90,7 @@ home nested=whiteboard/forrestdoc/build/ depend project=forrest-whiteboard-forrestdoc/ depend project=ant/ -depend project=ant-contrib/ +depend project=ant-contrib inherit=runtime/ depend project=xml-xerces/ depend project=xalan/ depend project=antlr/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
/home on brutus is full
Not sure what caused the sudden fill-up, but it is not me. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
help please with Gump Forrest
Finally Gump got through to the end of the food chain and built our base project for Forrest - yippee! Now our next failure is forrest-test ... --- BUILD FAILED ... /home/gump/workspaces2/public/workspace/forrest/main/targets/plugins.xml:243: Could not create task or type of type: for. Ant could not find the task or a class this task relies upon. ... --- We do have a depend entry for ant-contrib which provides that for task, but Gump does not seem to pick it up. Is our descriptor missing something, e.g. a nested entry for the ant or something? Sorry, i cannot figure it out. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: help please with Gump Forrest
Peter Janes wrote: David Crossley wrote: We do have a depend entry for ant-contrib which provides that for task, but Gump does not seem to pick it up. Is our descriptor missing something, e.g. a nested entry for the ant or something? Sorry, i cannot figure it out. ant-contrib recently removed the for task from the antcontrib.properties file, so the only way to get it is via antlib. for depends on Ant 1.6, which also introduced antlibs, so it's a way to enforce that version. There were several messages on their cvs list that said this will break a lot of builds, but when I last looked they seemed fine with that. Ah, wow, thanks. So Gump was just doing its job, and reporting issues to us. The way to fix the build is to use namespacing, which is also part of 1.6. First, remove the taskdef/ that loads the properties file. Then add a namespace definition to your project/ tag... project ... xmlns:antcontrib=antlib:net.sf.antcontrib and then use that namespace to prefix all of your ant-contrib tasks... antcontrib:for param=foo ... /antcontrib:for Hope this helps, Peter J. I expect that it will, thanks. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
forrest does not depend on struts, yet fail
Gump is telling us that it cannot build forrest due to a failed dependency on Struts. However we do not depend on on struts. Can anyone explain why this is happening? http://brutus.apache.org/gump/public/forrest/ http://brutus.apache.org/gump/public/forrest/forrest/details.html --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrest does not depend on struts, yet fail
Brett Porter wrote: forrest - cocoon - jakarta-turbine-jcs - struts good luck :) Hu'oh. Of course, thanks. The gump messages are confusing though. Cocoon is our broken dependency. We could easily follow through to see what is going on down the line. --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: brutus disk full again
Leo Simons wrote: [snip] ... It also looks like there's a sizeable amount of stuff from the forrest people that might be able to shrink a little. Not really. I had already trimmed it down as much as possible. I gather from watching the build-up to the upcoming Infrathon that the scheduled extra resources for brutus, and the other IBM-donated machines, is not likely to happen. Is there an alternative plan to get more disk space? --David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Gump3 Presentation -- choice of technology
Leo Simons wrote: Thomas wrote: More I have taken a look at the dynaGump but can't get it to woork the application is missing a Catalogmanager.properties. I've copied one from the samples of the cocoon source but don't know if I need configure it in anny special way. That has got to be the most common error or rather warning cocoon spits out. It should be able to work without that file. What do you see when visiting http://localhost:8080/? Ignore the CatalogManager.properties message. It is for adding your own catalog to look up extra DTDs for xml source documents, to save network trips and get a local copy. You can have an optional CatalogManager.properties in your project which can be empty and thus keep the thing quiet. What version of Cocoon is this? -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest Failures
Gav wrote: Thanks for the detailed explanation, helps a lot. Sounds like your still a fair way off Maven2 support then, I don't Know Maven and can not really help with that I don't think. What should Forrest (and possibly Lenya too) do about these errors, David at Forrest mentioned about changing cocoons gump descriptor, what is involved in this, Forrest uses Cocoon trunk which has changed to use Maven2. The previous comments related to Cocoon were about changing Cocoon's gump to use their 2.1 branch. That would directly help Lenya's Gump but not Forrest's. Actually it might help Forrest because at least we would get an attempt to build and it might show that we could revert to using Cocoon's 2.1 release branch. or should I talk to cocoon about it, I can not find any recent discussion about this so apologies if it has already been answered. ?? Searching for the word Cocoon found this: Re: Metadata for Cocoon not correct anymore http://thread.gmane.org/gmane.text.xml.cocoon.devel/63433 -David Turning the nag off seems a bit like taking the battery out of a smoke detector. Gav... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Forrest Failures
David Crossley wrote: Forrest uses Cocoon trunk which has changed to use Maven2. The previous comments related to Cocoon were about changing Cocoon's gump to use their 2.1 branch. That would directly help Lenya's Gump but not Forrest's. Actually it might help Forrest because at least we would get an attempt to build and it might show that we could revert to using Cocoon's 2.1 release branch. Hold that latter thought. I just tried changing Forrest's trunk to use Cocoon-2.1 and there is some work to do. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
use of ant-contrib fails, perhaps missing Ivy
Hello Gump people, help please. One of Forrest's projects started failing, as do others using ant-contrib, e.g. logging-log4cxx ... taskdef A class needed by class net.sf.antcontrib.net.URLImportTask cannot be found: fr/jayasoft/ivy/DependencyResolver... It seems to be related to when Ivy was added to the gump/metadata/project/ant-contrib.xml http://svn.apache.org/viewvc?view=revrevision=449569 -David Gump wrote: 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 forrest-whiteboard-forrestdoc has an issue affecting its community integration. This issue affects 2 projects, and has been outstanding for 19 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - forrest-whiteboard-forrestdoc : Apache Forrest is an XML standards-oriented documentation fr... - forrest-whiteboard-forrestdoc-autotest : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://vmgump.apache.org/gump/public/forrest/forrest-whiteboard-forrestdoc/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/forrest/forrest-whiteboard-forrestdoc/gump_work/build_forrest_forrest-whiteboard-forrestdoc.html Work Name: build_forrest_forrest-whiteboard-forrestdoc (Type: Build) Work ended in a state of : Failed Elapsed: 2 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/usr/local/gump/public/workspace/xml-xalan/build/serializer.jar:/usr/local/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=05102006 jar [Working Directory: /usr/local/gump/public/workspace/forrest/whiteboard/forrestdoc] CLASSPATH: /opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/forrest/whiteboard/forrestdoc/build/tools/ant:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/ant-contrib/target/ant-contrib-05102006.jar:/usr/local/gump/packages/bcel-5.2/bcel-5.2.jar:/usr/local/gump/packages/antlr-2.7.6/antlr.jar - Buildfile: build.xml [mkdir] Created dir: /x1/gump/public/workspace/forrest/whiteboard/forrestdoc/build/tools/ant [javac] Compiling 1 source file to /x1/gump/public/workspace/forrest/whiteboard/forrestdoc/build/tools/ant [javac] Note: /x1/gump/public/workspace/forrest/whiteboard/forrestdoc/src/ant/org/apache/forrest/tools/taskdefs/PathConvert.java uses unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. BUILD FAILED /x1/gump/public/workspace/forrest/whiteboard/forrestdoc/build.xml:46: taskdef A class needed by class net.sf.antcontrib.net.URLImportTask cannot be found: fr/jayasoft/ivy/DependencyResolver Total time: 2 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/forrest/forrest-whiteboard-forrestdoc/rss.xml - Atom: http://vmgump.apache.org/gump/public/forrest/forrest-whiteboard-forrestdoc/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 2205102006, vmgump.apache.org:vmgump-public:2205102006 Gump E-mail Identifier (unique within run) #21. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: use of ant-contrib fails, perhaps missing Ivy
Stefan Bodewig wrote: David Crossley wrote: Hello Gump people, help please. One of Forrest's projects started failing, as do others using ant-contrib, e.g. logging-log4cxx ... Yep, looks as if ant-contrib would require Ivy at runtime now. I've just marked it as a runtime dependency. It seems to be related to when Ivy was added to the gump/metadata/project/ant-contrib.xml http://svn.apache.org/viewvc?view=revrevision=449569 Well, that change just followed a change in ant-contrib. If your project uses ant-contrib during the build it will need to add inherit=runtime - like it should for any other dependency that it runs during the build. forrest always did, so it should work again with the next run. I've also fixed the log4cxx descriptor. Fantastic. Thanks Stefan, thanks Antoine. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Projects failing because there is no cocoon
Bill Barker wrote: From: Jan.Materne There are some projects - forrest - forrest-test - lenya which have dependency on cocoon. Message Bad Dependency. Project: cocoon unknown to *this* workspace Cocoons Gump-metadata is in project/cocoon/module.xml instead of project/cocoon.xml. Could that be a reason? No, it is because cocoon requires M2, so having it in Gump just generates a lot of failed build noise. Yes, it is a pity. At Forrest we are working on using Ivy and pre-built Cocoon jars. However that will take time, so we will just delete the projects forrest and forrest-test. Thanks to Gump for its excellent help in the past. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: metadata
Matt Benson wrote: (not subscribed; following responses on markmail and trying to maintain continuity by subject line alone) I get: ! /Users/mbenson/oss/asf svn co https://svn.apache.org/repos/asf/gump/metdata/project/ gump-metadata svn: URL 'https://svn.apache.org/repos/asf/gump/metdata/project' ^ s/metdata/metadata/ -David doesn't exist ! /Users/mbenson/oss/asf WTF? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Gump Wiki] Update of ... by ...
On Mon, Dec 22, 2008 at 05:00:33PM +, sebb wrote: On 22/12/2008, Sander Temme scte...@apache.org wrote: On Dec 22, 2008, at 7:53 AM, Apache Wiki wrote: The following page has been changed by buyyourall: Deleted, and (hopefully) banned. Of course all of this will be in the mail-archives... (S)he also spammed general and commons. I've added the offending hostname to the Apache section of general/BadContent so hopefully no more such spams will be possible. Damn wikis. It has happened again, just before Christmas. I deleted it today. It was from the same user. So does that mean that our banning techniques are ineffectve? I noticed something interesting ... On 22 Dec, Sander removed the spam XXX has bought the Then the diff for their edit of 24 Dec replaced the same stuff that Sander had already deleted. So i suppose that they edited an old diff and so got double value from our diff email system. Damn wikis. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
assistance with Apache Forrest
I did some research to find the ASF projects that manage their websites with Apache Forrest, and am sending similar email to each project's dev mail list. The purposes of this email are to remind people about some of the useful facilities of Forrest, and also alert them to discussion about the status and future directions of Forrest, and to appeal for people to assist Forrest. --- oOo --- These are useful facilities to assist with developing and managing a Forrest solution for your project's website. How to deploy documentation with the Forrestbot svn workstage This explains how the Forrest project manages our own documentation. http://forrest.apache.org/howto-forrestbot-svn.html Generate an ASF mirrors page using interactive web form http://forrest.apache.org/docs/dev/howto/howto-asf-mirror.html ForrestBar - Firefox toolbar to ease navigation and search of Forrest resources http://forrest.apache.org/tools/forrestbar.html How to do development with Apache Forrest http://forrest.apache.org/howto-dev.html Frequently Asked Questions http://forrest.apache.org/faq.html The Anakia output plugin This was developed to assist the old Incubator website to stop using Forrest and export all content to an Anakia xdoc format. From there it could used by an Anakia-based build system, or be further transformed. http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.output.Anakia/ As usual, if you need further assistance with anything then please ask on the Forrest mail lists. --- oOo --- There is discussion currently underway on the Forrest dev mail list about the current status and future direction of Forrest. http://thread.gmane.org/gmane.text.xml.forrest.devel/27325 If anyone can assist Forrest, in any capacity, then please do. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Self-Description of Gump
One concept that would be useful to work into that description ... The Gump notifications say: -- To whom it may engage... Project has an issue affecting its community integration. -- Gump tends to draw people across the project boundaries. We are continually made aware of the effects of changes as they happen, and can more easily report or help to fix things in the other project. I don't know how to add that to the description, without bloat. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: A Few Plans
Stefan Bodewig wrote: - ask the Forrest and Lenya communities which parts of Cocoon 2.x they need, remove the Cocoon reactor and only build the parts needed, finally start building Forrest and Lenya again. For Forrest, we use Cocoon-2.1 branch (i.e. the Ant-based build) and various blocks. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Cocoon for Forrest (was Re: A Few Plans)
Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: - ask the Forrest and Lenya communities which parts of Cocoon 2.x they need, remove the Cocoon reactor and only build the parts needed, finally start building Forrest and Lenya again. For Forrest, we use Cocoon-2.1 branch (i.e. the Ant-based build) and various blocks. Is there still any development on the 2.1 branch at all (bug fixes, whatever) It is sporadic. There has been some desire expressed on the Cocoon dev list to keep maintaining it. However only some commit activity has followed. or would it make sense to consider it stale and just package up the jars Forrest needs? Perhaps we could do that until there is further activity at Cocoon. Would someone please refer me to a useful example of a packaged gump project. Where would the packaged jars be stored? If we want to keep building Cocoon, can we identify the blocks that are needed and restrict the build to those? Yes. We would need the core, and then Forrest has the blocks listed in our existing gump descriptor (but commented out). By the way, so that people are clear. The current Gump run happening for cocoon is the Maven-based build of Cocoon trunk (i.e. Cocoon-2.2) and there is not yet any Gump run for the cocoon3. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Cocoon for Forrest
Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: - ask the Forrest and Lenya communities which parts of Cocoon 2.x they need, remove the Cocoon reactor and only build the parts needed, finally start building Forrest and Lenya again. For Forrest, we use Cocoon-2.1 branch (i.e. the Ant-based build) and various blocks. Is there still any development on the 2.1 branch at all (bug fixes, whatever) It is sporadic. There has been some desire expressed on the Cocoon dev list to keep maintaining it. However only some commit activity has followed. or would it make sense to consider it stale and just package up the jars Forrest needs? Perhaps we could do that until there is further activity at Cocoon. Would someone please refer me to a useful example of a packaged gump project. Where would the packaged jars be stored? One of the (many) pain points in Gump. Currently they are stored inside svn in a PMC private area - so we don't distribute a few things. I think I've added the blocks you need and a cocoon21 project that holds all necessary jars. Thanks. For Forrest, i will specifically add the depend stuff that we used to obtain via the old Cocoon-2.1 gump descriptor. Of course, it would be better if cocoon21 was being built by Gump. Both the Forrest and Cocoon communities can use assistance. Would it cause too much work for Gump? -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump for Cocoon3
Stefan Bodewig wrote: David Crossley wrote: and there is not yet any Gump run for the cocoon3. And added one for cocoon3. Thanks. I showed the Cocoon project: http://thread.gmane.org/gmane.text.xml.cocoon.devel/80891 -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Cocoon for Forrest
Stefan Bodewig wrote: Both the Forrest and Cocoon communities can use assistance. Just ask. :-) I meant the way Gump works to assist projects to help each other. Thanks too for the other assistance. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r960141 - /gump/metadata/project/forrest.xml
Stefan Bodewig wrote: David Crossley wrote: Use jing from our packaged supporting products until we get jing-trang happening with gump. Can you provide the details to try and build it inside Gump? I have not yet tried to investigate ... http://jing-trang.googlecode.com/svn/trunk/readme.txt -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump for Forrest
Please help with the descriptor for Forrest. I am trying to get forrest-core with the stuff that is required to build forrest. Most of those dependencies are also required to later run forrest. Then forrest-runtime which has the minimum additional stuff needed to actually run forrest. Then forrest-test-basic which builds a small site that should have no additional dependencies. Then forrest-test which builds a more complex site, which does have some additional dependencies. I just now added a change for the next run. See r960769 I also get the feeling that i am being a bit crude with the inheritance side of things. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump for Forrest
Stefan Bodewig wrote: David Crossley wrote: Please help with the descriptor for Forrest. I also get the feeling that i am being a bit crude with the inheritance side of things. You are not alone. I can tell you what I think it does, but must admit I'm not sure I get it right. depend and option have an inherit attribute which can mean: * If you use inherit=jars then the project that contains the depend tag seems to also contain the other project's jars as outputs of its own * If you use inherit=all the the project that contains the depend tag seems to also contain the other project's depend and option tags as dependencies of its own. * If you use inherit=runtime the the project that contains the depend tag seems to also contain the other project's depend and option that themselves have a runtime=true attribute tags as dependencies of its own. Many thanks. That explains well what i thought i understood. I am trying to get forrest-core with the stuff that is required to build forrest. Most of those dependencies are also required to later run forrest. Then forrest-runtime which has the minimum additional stuff needed to actually run forrest. I'd suggest you use runtime=true on all dependencies that are later required to run forrest inside the forrest-core project, remove forrest-runtime and use depend project=forrest-core inherit=runtime/ wherever you'd use forrest-runtime now. I think this should do what you intend. Yes. However, i wanted to enable forrest-core to build as easily as possible. Ah, now i see that that is where i would use option rather than depend for the things that i am defining as extra stuff for runtime. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Cocoon for Forrest
Stefan Bodewig wrote: One of the (many) pain points in Gump. Currently they are stored inside svn in a PMC private area - so we don't distribute a few things. I think I've added the blocks you need and a cocoon21 project that holds all necessary jars. Hi Stefan, pleae add the following block jars to the the cocoon21 package ... cocoon-auth-block.jar cocoon-lucene-block.jar cocoon-profiler-block.jar cocoon-template-block.jar cocoon-validation-block.jar cocoon-xsp-block.jar -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump for Forrest
I am getting closer. Using some from our own lib directory until it works, then will go back to address those. Unless i am reading incorrectly, Gump is taking 60+ minutes on forrest-test-basic. That seems strange. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump for Forrest
Stefan Bodewig wrote: David Crossley wrote: Unless i am reading incorrectly, Gump is taking 60+ minutes on forrest-test-basic. That seems strange. Both forrest-test-basic and forrest-test get killed by Gump - it terminates builds that take longer than an hour. For some reason your build never finishes - my guess is that the forked Jetty is never getting terminated if the application inside of it runs into an exceptional state and so Ant keeps waiting for it. Youch, sorry. I just commented out the forrest-test project until the forrest-test-basic is working. Is there a better way to disable a project, rather than simple xml comments? -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Forrest needs excalibur-instrument-api
The forrest-test-basic started failing after the move of Excalibur stuff. I think that excalibur-instrument-api is needed in the packaged-excalibur project. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Gump on adam.a.o trouble with Forrest build
Author: crossley Date: Thu Jan 6 00:18:08 2011 New Revision: 1055692 URL: http://svn.apache.org/viewvc?rev=1055692view=rev Log: Try setting sysproperty java.awt.headless true. While forrest does run okay on vmgump and on zone, on the adam.a.o Mac OS X it issues java.lang.InternalError: Can't connect to window server - not enough permissions and then hangs for one hour until killed. That did not fix it. Actually i see now that this is already set at the top level Host Configuration metadata/adam.xml Can anyone help to resolve this please. -David Modified: gump/metadata/project/forrest.xml Modified: gump/metadata/project/forrest.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/forrest.xml?rev=1055692r1=1055691r2=1055692view=diff == --- gump/metadata/project/forrest.xml (original) +++ gump/metadata/project/forrest.xml Thu Jan 6 00:18:08 2011 @@ -84,7 +84,9 @@ project name=forrest-test-basic !-- Build the seed-basic site, which utilises no plugins. -- -ant basedir=main target=test-basic/ +ant basedir=main target=test-basic + sysproperty name=java.awt.headless value=true/ +/ant depend project=forrest-core inherit=runtime/ depend project=commons-jxpath/ [ snip ] - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump on adam.a.o trouble with Forrest build
Stefan Bodewig wrote: I haven't looked at forrest's build file but I assume the java task you use to start Cocoon forks a new VM which does not see the system properties set for the VM used by Ant. Ah, i wondered about that. Yes it does. You could explicitly set the headless property in your java task or you can try to set the system property ant.build.clonevm[1] to true from inside your Gump descriptor (I'll do so shortly) which should copy over the system properties from Ant's VM including the headless one. The latter would be better. Thanks. -David Stefan [1] http://ant.apache.org/manual/clonevm.html - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump on adam.a.o trouble with Forrest build
David Crossley wrote: Stefan Bodewig wrote: I haven't looked at forrest's build file but I assume the java task you use to start Cocoon forks a new VM which does not see the system properties set for the VM used by Ant. Ah, i wondered about that. Yes it does. You could explicitly set the headless property in your java task or you can try to set the system property ant.build.clonevm[1] to true from inside your Gump descriptor (I'll do so shortly) which should copy over the system properties from Ant's VM including the headless one. The latter would be better. Thanks. That got past the hang on adam now thanks. Some new strangeness. We now need to require jakarta-regexp (on vmgump and zone too). We must have been getting this for free, prior to adding the clonevm. Anyway, added now in r1056590. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump on adam.a.o trouble with Forrest build
David Crossley wrote: David Crossley wrote: Stefan Bodewig wrote: I haven't looked at forrest's build file but I assume the java task you use to start Cocoon forks a new VM which does not see the system properties set for the VM used by Ant. Ah, i wondered about that. Yes it does. You could explicitly set the headless property in your java task or you can try to set the system property ant.build.clonevm[1] to true from inside your Gump descriptor (I'll do so shortly) which should copy over the system properties from Ant's VM including the headless one. The latter would be better. Thanks. That got past the hang on adam now thanks. Some new strangeness. We now need to require jakarta-regexp (on vmgump and zone too). We must have been getting this for free, prior to adding the clonevm. Anyway, added now in r1056590. Mmmm, things are getting worse since adding the clonevm. The forrest-test-basic project that used to work are now failing with configuration problems. I don't know how to debug this. Any ideas? Otherwise i think perhaps revert the metadata, get a build output when it is working again, save it. Then try again, and compare the broken output results. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Gump on adam.a.o trouble with Forrest build
Thanks so much for your help Stefan. I need to concentrate on the upcoming Forrest release. So i will return our gump descriptor to its previous working state (knowing that there are some glitches). Is there some way to stop the two projects just on adam.a.o that were causing it to hang for one hour each: (forrest-test-basic and forrest-test). I think that i have asked that before, and answer is no. Or to disable the complete Forrest on adam.a.o so as to not consume the resources. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Site Updated to Forrest 0.9
Stefan Bodewig wrote: now that Forrest 0.9 is released (congrats) I've upgraded our site to use it so we can get rid of our custom skin which we added for the trademark stuff. The changes are already on mino and will become visible soon[1]. I couldn't find any major differences but it would be good if anybody could double check to make sure the site still works as expected. I had a quick look using the proxy trick prior to rsync publish. It seems okay. http://apache.org/dev/project-site.html -David Stefan [1] Maybe it is time to use svnpubsub. In all the years I've modified the page I've never had a single case where we did not want a changed site to go live immediately. - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Help needed with ASF Branding Requirements
Stefan Bodewig wrote: I think we cover all the rest of the requirements - but I'll double check - except for our logos that need TM symbols. I'm still not capable of doing any artwork so please, who ever feels like using Gimp or Photoshop or Paint, you are more than welcome to TMify the bench logos (the one on our main site as well as the one on our reports). I am no graphics expert either. I started a Forrest plugin to assist with this. See config patch at GUMP-163 It overlays a trademark symbol using SVG to create a new image. This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. Tweak its related SVG file to position its TM appropriately. Hope that helps. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Help needed with ASF Branding Requirements
Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: I think we cover all the rest of the requirements - but I'll double check - except for our logos that need TM symbols. I'm still not capable of doing any artwork so please, who ever feels like using Gimp or Photoshop or Paint, you are more than welcome to TMify the bench logos (the one on our main site as well as the one on our reports). I am no graphics expert either. I started a Forrest plugin to assist with this. See config patch at GUMP-163 Many many thanks. However, i noticed yesterday (at Forrest) that the generated PNG has changed colour. Same for Gump. Drat. (FOR-1226) We have been needing to update the Batik used by both Cocoon and Forrest for some time. Perhaps that will help. It overlays a trademark symbol using SVG to create a new image. IIUC we could merge the overlay directly into the logo, is that correct? I'm not familiar with SVG at all but maybe that needs to change anyway. Yes it could. This plugin was just a simple solution to take an existing PNG and generate a new PNG. Yes looking now at the gump-logo-original.svg it would be relatively easy to add the text element directly into that SVG. This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. I think it is bench.svg, but I'm not sure. Tweak its related SVG file to position its TM appropriately. I was only considering doing as above to generate a new PNG from the old PNG. Yes amending the SVG directly would be better. -David I'll give it a try. Hope that helps. Thanks again Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Help needed with ASF Branding Requirements
Stefan Bodewig wrote: Stefan Bodewig wrote: Stefan Bodewig wrote: David Crossley wrote: This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. I think it is bench.svg, but I'm not sure. No, it is not. bench.svg doesn't include the feather above the bench. No idea what the source of the reports logo is, it likely isn't in svn. I'll see whether I manage to extract the feather from the site logo by diffing bench.svg and the site logo's svg. No chance without making myself more familiar with SVG first, which won't happen too soon. Both files refer to asf-logo.svg that I don't find anywhere and I think this is the one that pulls the feather in. It is displayed in one and not displayed in the other. Yes, using one SVG2PNG viewer i see that there is an error symbol (on both images) where that included SVG is supposed to be. The reason that the Feather is seen on the gump-logo-original.svg is that SVG code to create the feather is also in this file. GUMP-164 -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
strange DATE in Gump
While trying to debug a Gump run, i noticed some jars in the classpath with strange filenames, e.g. ant-contrib-20122012.jar I presume that that is expanded from the @@DATE@@ in project/ant-contrib.xml Should that be MMDD so 20121220? -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
help with forrest-test gump run
Help please with working out why the forrest-test run of Gump is broken. http://vmgump.apache.org/gump/public/forrest/forrest-test/ In a local build, this works fine (cd main; ./build.sh test -v). However, with the Gump run, it skips over a certain step which causes later things to fail. In the Project build output, search for Ant target fetch-local-unversioned-plugin. (The run is in verbose mode.) At this target, after that echo it is supposed to be then doing the target get-local via an antcallback [1] around line # 70. This is coming from the fetch-plugin target via a sequential antfetch [2] around line # 349. [1] https://svn.apache.org/repos/asf/forrest/trunk/main/var/pluginlist2fetch.xsl [2] https://svn.apache.org/repos/asf/forrest/trunk/main/targets/plugins.xml That all works properly at the local build. However running via Gump, it completely misses that get-local target, with no error message. Can anyone see what is wrong for Gump please? FOR-1235 -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: help with forrest-test gump run
Martin Gainty wrote: i think you have located a failing corner-case for antcallback as a workaround instead of invoking antcallback antcallback target=get-local return=plugin-found try using the depends attribute target name=testCallback description=Test CallBack depends=get-local http://ant-contrib.sourceforge.net/tasks/tasks/antcallback_task.html Thanks. The Forrest build system utilises that in a number of different places. Rather than disrupting that at this stage, i intend to try a different approach for getting Gump to exercise our stuff. Thanks again for your assistance. -David Martin __ Date: Fri, 21 Dec 2012 23:45:59 +1100 From: cross...@apache.org To: general@gump.apache.org Subject: help with forrest-test gump run Help please with working out why the forrest-test run of Gump is broken. http://vmgump.apache.org/gump/public/forrest/forrest-test/ In a local build, this works fine (cd main; ./build.sh test -v). However, with the Gump run, it skips over a certain step which causes later things to fail. In the Project build output, search for Ant target fetch-local-unversioned-plugin. (The run is in verbose mode.) At this target, after that echo it is supposed to be then doing the target get-local via an antcallback [1] around line # 70. This is coming from the fetch-plugin target via a sequential antfetch [2] around line # 349. [1] https://svn.apache.org/repos/asf/forrest/trunk/main/var/pluginlist2fetch.xsl [2] https://svn.apache.org/repos/asf/forrest/trunk/main/targets/plugins.xml That all works properly at the local build. However running via Gump, it completely misses that get-local target, with no error message. Can anyone see what is wrong for Gump please? FOR-1235 -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: help with forrest-test gump run
Stefan Bodewig wrote: David Crossley wrote: Help please with working out why the forrest-test run of Gump is broken. http://vmgump.apache.org/gump/public/forrest/forrest-test/ Sorry, have been (and likely will continue to be for the next few days) mostly offline. Thanks, me too. You have modified the build process enough that there is no fetch-local-unversioned-plugin target to see in the log anymore. Yep, i am trying a completely different approach now. Deploying the plugins, then forcing the test to use them rather than forrest's fancy plugin finding mechanism. Right now I see configure-plugin failing for PDF - is the where you'd suppose the plugin to be downloaded? It is different now :-) This is fine, as i am gradually working to fix various things that Gump encounters. I reckon that it is on the home straight. Looking through FOR-1235 and your XSL, you have target name=fetch-local-unversioned-plugin unless=plugin-found which means the target would be skipped if the property plugin-found was set for any reason. The Gump output you quote inside the JIRA ticket really looks like the one you'd get if a target was skipped because of an if/unless attribute. Drat, i should have updated the issue with a snippet from a more recent Gump run. I think that it got past that stage but completely missed the next get-local. After this new approach is settled, i hope to make some time. Of course the challenge is to work out why the difference between a local build and the Gump one. You certainly could be triggering a bug/feature in Ant or Ant-Contrib present only in trunk but not the version you use locally, but neither project has been really active lately so that's not too likely. Maybe you could build Ant from trunk and see whether your local build still fails with that as well. Good idea. It has been a while since Forrest upgraded various dependencies, so a job that needs doing anyway. Thanks again for your efforts Stefan. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Your Gump Build(s)
Stefan Bodewig wrote: Dear Community Apache Gump builds some of your projects and it is quite possible you don't know or have by now forgotten about it. More than half a year ago a technical problem has forced us to turn off emails on build failures as we would have been sending out lots of false alarms. Before we re-enable emails we'd like to know whether you are still interested in the service Gump provides, so please tell us. :-) Sorry for the late reply. Yes, if possible then Apache Forrest would like to continue. Forrest is a consumer of many other projects. Our gump metadata have been configured to utilise our local copy of some of those. For others we use the gump-built one. Gump has a special copy of Cocoon-2.1 but we could change to use the abovementioned approach. So Forrest could re-jig ours to use the up-to-the-minute version of whatever Gump does provide, and then use our local copies for the rest. -David Metadata for many projects have been neglected for a long time and it is quite possible they'd need some love for results to be meaningful. All Apache committers have write access to Gump's metadata. In case you don't know what this Gump stuff is about: Apache Gump builds the full stack of the latest commits of software in order to ensure integrity over releases. Build failures surface API discontinuities between projects before they impact releases, and Gump's e-mail notifications hope to promote the conversations between teams to resolve those discontinuities. When responding to this mail please shorten the CC list as appropriate. Cheers Stefan on behalf of the Gump PMC - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r1509547 - /gump/metadata/project/tomcat-trunk.xml
Author: billbarker Date: Fri Aug 2 05:16:04 2013 New Revision: 1509547 URL: http://svn.apache.org/r1509547 Log: dbcp build is now integrated into the regular tomcat build Modified: gump/metadata/project/tomcat-trunk.xml Modified: gump/metadata/project/tomcat-trunk.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/tomcat-trunk.xml?rev=1509547r1=1509546r2=1509547view=diff == --- gump/metadata/project/tomcat-trunk.xml (original) +++ gump/metadata/project/tomcat-trunk.xml Fri Aug 2 05:16:04 2013 @@ -27,6 +27,7 @@ svn repository=asf dir=tomcat/trunk/ + mkdir dir=tomcat-deps / The metadata validation system does not like that mkdir being outside of a project. Do 'cd metadata; ./validate' Is it just a remnant of the stuff that was removed? -David project name=tomcat-trunk packageorg.apache.catalina/package ant @@ -42,12 +43,12 @@ property name=tomcat-native.tar.gz project=commons-daemon id=native-distro reference=outputpath / property name=junit.jar project=junit reference=jarpath id=junit / - property name=commons-pool.home project=commons-pool - path=. / - property name=commons-dbcp.home project=commons-dbcp - path=. / - property name=tomcat-dbcp.home project=tomcat-trunk-dbcp - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Checkstyle (svn commit: r1552445 - /gump/metadata/project/xml-fop.xml)
Hi, i see that Tomcat also use Checkstyle. If you continue to have trouble, then perhaps look at how they do it. cd $SVN/gump/metadata/project/ grep checkstyle *.xml Hope that helps. -David vhenneb...@apache.org wrote: Author: vhennebert Date: Thu Dec 19 22:24:55 2013 New Revision: 1552445 URL: http://svn.apache.org/r1552445 Log: Second attempt to fix Checkstyle dependencies by adding them directly to the FOP descriptor Modified: gump/metadata/project/xml-fop.xml Modified: gump/metadata/project/xml-fop.xml URL: http://svn.apache.org/viewvc/gump/metadata/project/xml-fop.xml?rev=1552445r1=1552444r2=1552445view=diff == --- gump/metadata/project/xml-fop.xml (original) +++ gump/metadata/project/xml-fop.xml Thu Dec 19 22:24:55 2013 @@ -69,7 +69,12 @@ sysproperty name=ant.build.clonevm value=true/ property name=checkstyle.location project=checkstyle reference=jarpath id=checkstyle/ /ant -depend project=checkstyle inherit=runtime/ +depend project=checkstyle/ +depend project=commons-beanutils/ +depend project=commons-cli/ +depend project=commons-exec/ +depend project=commons-validator/ +depend project=google-guava / depend project=xml-fop inherit=all/ depend project=fop-hyph/ depend project=junit/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: svn commit: r1659380 - /gump/metadata/project/openssl-1.0.2.xml
On Thu, Feb 12, 2015 at 07:56:01PM -, rj...@apache.org wrote: Author: rjung Date: Thu Feb 12 19:56:01 2015 New Revision: 1659380 URL: http://svn.apache.org/r1659380 Log: Add OpenSSL 1.0.2 branch. [snip] + url href=http://www.openssl.org// + description +OpenSSL Encryption Library (Branch 1.0.2) + /description + + git repository=github dir=/openssl/openssl branch=OpenSSL_1_0_2-stable/ There is no attribute branch in metadata/dtd/project.dtd so doing 'cd metadata; ./validate' fails. Is this attribute used by gump? If so then we can add it. -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Board Report Draft
On Sun, Jun 07, 2015 at 05:55:25PM +0200, Stefan Bodewig wrote: Hi all https://wiki.apache.org/gump/Drafts/BoardReports/20150617 I'll send it around the 10th, please add/correct/modify/remove as you see fit. Is there a mistake with this paragraph of the report? As more long running test projects have been added we needed to change vmgump's configuration back to perform four runs a day rather than three - where in fact we'll only manage two per day. A single run of Gump currently takes about eight and a half hours. Should it instead say perform three runs a day rather than four? http://gump.apache.org/#When+does+Gump+run? -David - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] Created: (GUMP-162) Doc: Remove the feedback from bottom strip, fix link colours in footer
Doc: Remove the feedback from bottom strip, fix link colours in footer -- Key: GUMP-162 URL: https://issues.apache.org/jira/browse/GUMP-162 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Priority: Minor The attached patch-gump-skinconf.txt removes the feedback link and fixes the CSS colours for the links in footer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] Updated: (GUMP-162) Doc: Remove the feedback from bottom strip, fix link colours in footer
[ https://issues.apache.org/jira/browse/GUMP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley updated GUMP-162: Attachment: patch-gump-skinconf.txt Doc: Remove the feedback from bottom strip, fix link colours in footer -- Key: GUMP-162 URL: https://issues.apache.org/jira/browse/GUMP-162 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Priority: Minor Attachments: patch-gump-skinconf.txt The attached patch-gump-skinconf.txt removes the feedback link and fixes the CSS colours for the links in footer. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Created] (GUMP-163) patch for forrest config to apply trademark to logos
patch for forrest config to apply trademark to logos Key: GUMP-163 URL: https://issues.apache.org/jira/browse/GUMP-163 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Use the new Forrest logo input plugin to apply a trademark. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Updated] (GUMP-163) patch for forrest config to apply trademark to logos
[ https://issues.apache.org/jira/browse/GUMP-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley updated GUMP-163: Attachment: logo-tm.txt The patch provides the SVG template file. It also configures the logo input plugin in the forrest.properties file. It changes the skinconf. Perhaps this would only be temporary until satisfied with the new image. See documentation (when the plugin and docs are published) at http://forrest.apache.org/pluginDocs/ patch for forrest config to apply trademark to logos Key: GUMP-163 URL: https://issues.apache.org/jira/browse/GUMP-163 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Attachments: logo-tm.txt Use the new Forrest logo input plugin to apply a trademark. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Commented] (GUMP-163) patch for forrest config to apply trademark to logos
[ https://issues.apache.org/jira/browse/GUMP-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13047120#comment-13047120 ] David Crossley commented on GUMP-163: - Forgot to publish the index page (done now, awaiting rsync) but the plugin docs are available directly at: http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.logo/ and the plugin has been deployed. patch for forrest config to apply trademark to logos Key: GUMP-163 URL: https://issues.apache.org/jira/browse/GUMP-163 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Attachments: logo-tm.txt Use the new Forrest logo input plugin to apply a trademark. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
[jira] [Created] (GUMP-164) Add trademark symbol to the SVG files that can produce the Gump logo images
Add trademark symbol to the SVG files that can produce the Gump logo images --- Key: GUMP-164 URL: https://issues.apache.org/jira/browse/GUMP-164 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Add a text element to the Gump logo SVG files. Here are the images and the SVG source which relates to each: 1) the gump-logo.png for the main website: src/documentation/content/xdocs/images/gump-logo-original.svg 2) the gump-logo.png for the Gump results reports: src/documentation/content/xdocs/images/bench.svg -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
