BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters, The following 7 notifys should have been sent *** G U M P [EMAIL PROTECTED]: Module lenya success, but with warnings. [EMAIL PROTECTED]: Project nant (in module nant) failed [EMAIL PROTECTED]: Module struts success, but with warnings. [EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5) success, but with warnings. [EMAIL PROTECTED]: Project asm (in module asm) failed [EMAIL PROTECTED]: Project jtidy-cvs (in module jtidy) failed [EMAIL PROTECTED]: Project JacORB (in module JacORB) failed *** G U M P [EMAIL PROTECTED]: Module lenya 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] Module lenya contains errors. The current state of this module is 'Success'. Full details are available at: http://brutus.apache.org/gump/public/lenya/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -ERROR- *** Failed to update from source control. Stale contents *** The following work was performed: http://brutus.apache.org/gump/public/lenya/gump_work/update_lenya.html Work Name: update_lenya (Type: Update) Work ended in a state of : Failed Elapsed: 1 min 41 secs Command Line: svn --quiet update --non-interactive lenya [Working Directory: /usr/local/gump/public/workspace/cvs] - svn: Working copy 'lenya/src/webapp/lenya/resources/bxe/plugins' not locked - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/lenya/rss.xml - Atom: http://brutus.apache.org/gump/public/lenya/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3807012005, brutus:brutus-public:3807012005 Gump E-mail Identifier (unique within run) #1. *** G U M P [EMAIL PROTECTED]: Project nant (in module nant) 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 nant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 44 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - nant : NAnt is a free .NET build tool. In theory it is kind of like... Full details are available at: http://brutus.apache.org/gump/public/nant/nant/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 The following work was performed: http://brutus.apache.org/gump/public/nant/nant/gump_work/build_nant_nant.html Work Name: build_nant_nant (Type: Build) Work ended in a state of : Failed Elapsed: 3 secs Command Line: make [Working Directory: /usr/local/gump/public/workspace/nant] - mono bin/NAnt.exe -f:NAnt.build build Compat mode: the request from /home/gump/workspaces2/public/workspace/nant/bin/log4net.dll to load System was remapped (http://www.go-mono.com/remap.html) Compat mode: the request from /home/gump/workspaces2/public/workspace/nant/bin/log4net.dll to load System.Data was remapped (http://www.go-mono.com/remap.html) Compat mode: the request from /home/gump/workspaces2/public/workspace/nant/bin/log4net.dll to load System.Web was remapped (http://www.go-mono.com/remap.html) NAnt 0.85 (Build 0.85.1812.0; dev; 12/17/2004) Copyright (C) 2001-2004 Gerry Shaw http://nant.sourceforge.net BUILD FAILED The current runtime framework 'mono-1.0' is not correctly configured in the NAnt configuration file. Unable to locate 'mono' module using pkg-config. Download the Mono development packages from http://www.mono-project.com/downloads/. For more information regarding the cause of the build failure, run the build again in debug mode. Try 'nant -help' for more information make: *** [build-nant] Error 1 - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/nant/nant/rss.xml - Atom: http://brutus.apache.org/gump/public/nant/nant/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3807012005, brutus:brutus-public:3807012005 Gump E-mail Identifier (unique within run) #2.
The Gump3 branch
Hi gang! Phew, have I been busy :-D. I've gotten the Gump3 branch into a state where everything "works" (for me), as far as stuff is implemented. The main "core" thing that is missing is cyclic dependency detection. I've got the right algorithm written down on paper, just need to make it happen. The hooks for it are there already though (the gump.engine.modeller.Verifier class). I'm not going to describe everything that I built so far right now; I'd much rather see people reading through the code a little and trying to figure that out. It should all be much simpler to understand, especially for java buffs as a lot of stuff I did is deliberately very java-like. The other stuff that's missing is a lot of plugins. The new architecture as I set things up identifies three stages: - preprocessing - build/run - postprocessing And each of those can have plugins (basically what are now called actors). Preprocessing plugins that need to be built include source repository updaters. Build tools that need to be built include all the handlers for the different Commands. Postprocessing that needs to be built include the dynagump adapter. Basically everything :-D. Those people that know the current pygump should no doubt see how so many things are similar. However, there's also a lot of differences, small and big. The big ones IMHO are: * components. Most stuff is implemented as a component. Dependencies and config is passed into components through __init__. This leads to * clearly identified roles and responsibilities. Components are much smaller and do much less. This again leads to * Testable code. Though I haven't started writing tests yet, that will be easy now. For example, there's but two places in gump where we write to files (the bootstrap logger and the VFS layer) directly. Swapping in place a StringIO buffer is trivial. * consistency. Everything fits together in the same way. Its all components, with some of them plugins. * model symplification. The gump2 gump.model package is huge and kind-of difficult to grasp. All the difficult bits are now elsewhere. This makes it a lot easier to write plugins. * it doesn't work! Gump2 actually runs, and runs relatively quickly (being multi-threaded and all). Running Gump3 right now only results in some logging output. So what we have in Gump3 right now is three empty shells (a blank "pygump", a blank "dynagump" and a blank database) that should be able to do just about anything after they're filled with the right components. What I would like now is a beer and some feedback :-D Cheers, - Leo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: FrequentlyAskedQuestions
Date: 2005-01-07T16:30:03 Editor: BrettPorter Wiki: Gump Wiki Page: FrequentlyAskedQuestions URL: http://wiki.apache.org/gump/FrequentlyAskedQuestions no comment Change Log: -- @@ -24,6 +24,9 @@ }}} + '''Q: How do I match my Maven IDs to Gump IDs?''' + '''A:''' while efforts are underway to synchronize these identifiers, there are several incompatibilities. Please refer to the MavenId page to match your IDs, or help the effort by adding discovered incompatibilites. + = Gump debugging = '''Q: can we get access to the build outputs of the gump run?''' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] New: MavenId
Date: 2005-01-07T16:33:59 Editor: BrettPorter Wiki: Gump Wiki Page: MavenId URL: http://wiki.apache.org/gump/MavenId no comment New Page: = Gump and Maven ID mismatches = This page lists the known incompatibilies between Maven ang Gump IDs, and can be used as a resource to map them within your own project. See the [http://maven.apache.org/reference/plugins/gump/ Maven Gump Plugin] documentation for more information. If you know of any other incompatibilities, please add them to this list. Maven Gump|| || Group ID || Artifact ID || Project ID || Jar ID || || ... || ... || ...|| ...|| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: MavenId
Date: 2005-01-07T17:06:33 Editor: BrettPorter Wiki: Gump Wiki Page: MavenId URL: http://wiki.apache.org/gump/MavenId no comment Change Log: -- @@ -6,6 +6,24 @@ If you know of any other incompatibilities, please add them to this list. - Maven Gump|| -|| Group ID || Artifact ID || Project ID || Jar ID || -|| ... || ... || ...|| ...|| + Maven Gump || +|| Group ID || Artifact ID || Project ID || Jar ID || +|| avalon-framework || avalon-framework || avalon-framework-api || - || +|| axis || axis || ws-axis || axis|| +|| jaf || activation || jaf || - || +|| javamail || mail || javamail || - || +|| jaxrpc || jaxrpc-api || ws-axis || axis-jaxrpc || +|| jetty|| jetty|| jetty4 || - || +|| jstl || jstl || jakarta-taglibs-standard || - || +|| log4j|| log4j|| logging-log4j|| - || +|| msv || isorelax || iso-relax|| - || +|| msv || relaxngDatatype || relaxng || - || +|| ojb || ojb || db-ojb || - || +|| oro || oro || jakarta-oro || - || +|| saaj || saaj-api || ws-axis || axis-saaj || +|| servletapi || servletapi || jakarta-servletapi-5-servlet || - || +|| swt || swt || eclipse || swt || +|| velocity || velocity || jakarta-velocity || - || +|| xerces || xerces || xml-xerces || - || +|| ... || ... || ... || ... || + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: MavenId
Date: 2005-01-07T17:17:04 Editor: BrettPorter Wiki: Gump Wiki Page: MavenId URL: http://wiki.apache.org/gump/MavenId no comment Change Log: -- @@ -10,16 +10,19 @@ || Group ID || Artifact ID || Project ID || Jar ID || || avalon-framework || avalon-framework || avalon-framework-api || - || || axis || axis || ws-axis || axis|| +|| bouncycastle || bcprov-jdk14 || bcprov || - || || jaf || activation || jaf || - || || javamail || mail || javamail || - || || jaxrpc || jaxrpc-api || ws-axis || axis-jaxrpc || || jetty|| jetty|| jetty4 || - || || jstl || jstl || jakarta-taglibs-standard || - || || log4j|| log4j|| logging-log4j|| - || +|| logkit || logkit || avalong-logkit || logkit || || msv || isorelax || iso-relax|| - || || msv || relaxngDatatype || relaxng || - || || ojb || ojb || db-ojb || - || || oro || oro || jakarta-oro || - || +|| regexp || regexp || jakarta-regexp || - || || saaj || saaj-api || ws-axis || axis-saaj || || servletapi || servletapi || jakarta-servletapi-5-servlet || - || || swt || swt || eclipse || swt || - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Gump Wiki] Updated: MavenId
Date: 2005-01-07T18:40:34 Editor: BrettPorter Wiki: Gump Wiki Page: MavenId URL: http://wiki.apache.org/gump/MavenId no comment Change Log: -- @@ -1,6 +1,46 @@ -= Gump and Maven ID mismatches = += Gump and Maven IDs = -This page lists the known incompatibilies between Maven ang Gump IDs, and can be used as a resource to +== About the ID structures == + +Here, I will refer to a an artifact as a single buildable entity - eg, a JAR. + +In Maven, there are two identifiers for each artifact: + * group ID - this is a globally unique identifier for your product (eg velocity, gump or maven) + * artifact ID - this is an identifier unique within your group ID, for each artifact (eg velocity, velocity-utils) + +In Gump, there are also two identifiers for each artifact: + * project ID - this is a globally unique identifier for the SCM checkout and build to execute + * JAR ID - for each artifact built by the project + +There is also a module name, however this is not taken into consideration when identifying the artifact. + +== Known Issues == + +There are two issues at present in matching these concepts: + 1. the project ID naturally maps to artifact ID in maven, as Maven only generates one artifact per build descriptor. This is a mismatch losing the information in group ID from Maven and JAR ID from Gump + 2. when artifact and project map one-to-one, they sometimes differ as they were created independantly in Gump and Maven. + +To solve (2), the potential solutions are just to rename the projects in Maven, or rename them in Gump. It makes sense to do this in gump as most of the +metadata is centralised in gumps CVS, and the gump project will see projects and be able to assist projects to update. Neither is possible in Maven: users would need to be educated to update their project descriptors. This is still a problem that will be taken on later as part of the [http://wiki.apache.org/ASFRepository ASF repository] project. + +To solve (1), one of the following can be done: + * A policy in gump where project matches the definition of group ID. Maven projects would have to run a multiproject build, and each JAR listed with a JAR ID that matches artifact ID. While this requires no code changes, the problems with this are: + * incompatible with some Maven builds + * incompatible with existing gump descriptors + * if a single JAR build fails, the whole project fails, potentially causing less of gump to execute + * Code changes to gump to match the Maven ID scheme. The only one of the above problems present in this solution is that gump descriptors will possibly need updating. + +=== Implementing the Changes in Gump === + +If this is done, this is a potential solution. + + 1. Change module to match the group ID definition, and project to match the artifact ID definition. + 2. When a build generates multiple JARs, each will be allocated a new artifact ID, rather than a JAR ID. + 3. dependencies will then depend on just an artifact Id. + +== Mapping List == + +This section lists the known incompatibilies between Maven ang Gump IDs, and can be used as a resource to map them within your own project. See the [http://maven.apache.org/reference/plugins/gump/ Maven Gump Plugin] documentation for more information. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
gump and Maven IDs
Hi, http://wiki.apache.org/gump/MavenId I've started a list of known incompatibilities (by no means incomplete), listed my understanding of the problem, and potential solutions. Essentially, the core of the problem is that gump descriptors use the definition of a project inconsistently. eg. asm is one project with multiple jars; commons-jelly is multiple projects with one jar each. These otherwise are the same, so the gump descriptors should be defined the same way - and either way is possible with Maven and Ant (though both may require changes to some projects to do it). I think the latter is better, and have listed the reasons in the wiki entry (in particular, the ability to isolate breakages). I think the best solution is actually to change the way gump does the descriptors (also explained on the page). Any thoughts on what the best path is? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Gump Maven Plugin 2.0 Released
We are pleased to announce the Maven Gump Plug-in 2.0 release! http://maven.apache.org/reference/plugins/gump/ Changes in this version include: New Features: o Add maven.gump.module.name property for overriding the module name o Add junitreport element to the descriptor o Add multiproject module for generating a single module with several projects within the one descriptor. o Add nag element at module level Issue: MPGUMP-3. o Handle subversion as an SCM type Fixed bugs: o Set maven.final.name as a property for the <maven element, instead of final.name o Set http://www.ibiblio.org/maven -DgroupId=maven -DartifactId=maven-gump-plugin -Dversion=2.0 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-gump-plugin-2.0.jar Have fun! -The Maven Gump Plug-in development team --- Sent using Email 2.3.0 http://email.cleancode.org Sent on: Sat, 08 Jan 2005 14:20:40 AUSEST On System: CYGWIN_NT-5.1 1.5.12(0.116/4/2) i686 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: The Gump3 branch
> What I would like now is a beer and some feedback :-D First feedback ... my ailing 802.11b WISP network practically puked on all those Cocoon JARS. Yikes! I had to give up on Eclipse SVN and use command line SVN so as not to time out. 4+ hours (on third try) and counting. And no, I won't move to the flatlands, the mountains are worth this pain. Perhaps I ought re-install the modem... More (and hopefully useful) feedback once I've been able to play with this. Thanks for all your efforts on this. I'm excited to see what you've injected... regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]