Agreed! Nobody said that GUMP has to be the only proposal. As many
proposals as possible then use the best from all to enhance the project...
I'd like to try and keep the project definitions (projects/*.xml) the same
between proposals (saves on updates) but still...
> -----Original Message-----
> From: Nick Chalko [mailto:[EMAIL PROTECTED]]
> Sent: Friday, 09 March 2001 8:00 pm
> To: '[EMAIL PROTECTED]'
> Subject: RE: [GUMP] Ant-based GUMP
>
>
> Lets get this in the CVS tree under proposal so we can help!
>
> -----Original Message-----
> From: Scott Sanders [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 09, 2001 10:59 AM
> To: [EMAIL PROTECTED]
> Subject: Re:[GUMP] Ant-based GUMP
>
>
> Responding to a private email...
>
> Sorry I have been so quiet on the list. ;-(
>
> I had some different ideas on where Gump needed to go, so I pursued
> them. I needed Gump to help me in producing a helpful Extreme
> Programming environment, meaning continual building and posting of
> results, more like the Mozilla tinderbox, but in Java/Ant, as all my
> programming is in Java with Ant as the build tool. I am happy to post
> what I have done, as I use MANY (Batik, Xerces, Xalan, Ant, Log4J,
> Regexp, Slide, Tomcat) apache projects for my work and would like to
> give back to the community. But Sam was doing an excellent job at
> Gump for what he wanted, and I just decided to stay in the background
> for a while and flesh out my idea of a tinderbox, and then help to
> merge Alexandria/Gump/My version together. If you guys want me to
> come out of hiding, just let me know ;-)
>
> Right now, I have converted the initial script to be ant-based, so you
> call ant to kick the whole thing off. But after that, the initial Ant
> script initiates the rest of the process. My need was for Gump to be
> a Mozilla-type of tinderbox, one that builds over and over and over
> and keeps reporting the results. I also want all of the results to be
> XML-based, with an XSL stylesheet that converts to HTML on the
> client-side (IE5 for now). I currently use Saxon as the XSL
> processor, since I was getting many errors using Xalan, and most of my
> experience was with Saxon.
>
> The second step was to convert the stylesheets in the Gump process to
> output ant scripts. I kept the merge.xsl and the sortdep.xsl and
> started building a stylesheet to build the scripts to get from cvs and
> start building. I finished that sort of. It worked for a few of the
> projects.
>
> Right now the build scripts get from cvs and then build each project,
> rather than cvsing all and then building all. I am working on a way
> to let Ant know if a dependency earlier in the chain failed, so that
> it will not continue as the current Gump does.
>
> That is where I made it to. All HTML output does not work, and
> nothing is automated (ie repetitive builds).
>
> My intention was to run all of Sam's project definitions and all of my
> project definitions on my box ant home repetitively with
> Alexandria/Gump/my version, so I have all the JavaDoc, build results,
> jar files, etc. available at my fingertips. I also intended on this
> turning into a sort-of CPAN type jar distribution system.
>
> Let me know,
>
> Scott Sanders
>
> ----- Original Message -----
> From: "John Morrison" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, March 09, 2001 10:10 AM
> Subject: [GUMP] Ant-based GUMP
>
>
> > Would/could you please tell me/the list where you have gotten to on
> this
> > project?
> >
> > Thanks,
> >
> > John.
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
