You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Adam R. B. Jack" <aj...@trysybase.com> on 2003/12/13 00:48:19 UTC

Best Practices

Can I get more contributions for this?

http://jakarta.apache.org/gump/metadata/practices.html

[BTW: I've already fixed most of the formatting uglies &
property!=option/depend. So tips only please..]

Stefan, if you are undecided about some of these, feel free to mention it &
I'll de-emphasize them.

regards

Adam
--
Experience the Unwired Enterprise:
http://www.sybase.com/unwiredenterprise
Try Sybase: http://www.try.sybase.com


Re: Best Practices

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
Stefan wrote:

> I'm currently lacking a forrest installation and wouldn't know how to
> generated the pages anyway, that's why I've just changed the source
> XML (ran ispell over it).

Forrest/Python, I'm just not taking Gump to your sweet spot am I? ;-)
Seriously, sorry.

I guess I just assumed Forrest was becoming the defacto standard at
apache, but maybe I'm now learning that no such exists. :-) Oh well.

No worries on not be forrest savvy, I'll get Gump in a forrestbot one way or
another eventually & then none of us will need to be.

Thanks for the contributions.

regards

Adam


Re: Best Practices

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.

> On 15 Dec 2003, Stefan Bodewig <bo...@apache.org> wrote:
>
> > Re: don't create full distributions
>
> And given Gump's <javadoc> element, creating javadocs shouldn't be
> labeled "unnecessary work" IMHO.

This seems more like an argument for a javadoc-bot Gump (like a forrest-bot
Gump) to me. IMHO we need to explore alternative Gumps and keep the main one
focused on continuous integration.

regards,

Adam


Re: Best Practices

Posted by Stefan Bodewig <bo...@apache.org>.
On 15 Dec 2003, Stefan Bodewig <bo...@apache.org> wrote:

> Re: don't create full distributions

And given Gump's <javadoc> element, creating javadocs shouldn't be
labeled "unnecessary work" IMHO.

Stefan

Re: Best Practices

Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 12 Dec 2003, Adam R. B. Jack <aj...@trysybase.com> wrote:

> http://jakarta.apache.org/gump/metadata/practices.html

I'm currently lacking a forrest installation and wouldn't know how to
generated the pages anyway, that's why I've just changed the source
XML (ran ispell over it).

Re: don't create full distributions

Ant used Gump as its nightly build machine, so did some other projects
(JMeter and OJB IIRC).  I think this is OK, but should be a separate
project definition.  And projects doing so should be aware that they
may not get a nightly build if one of the projects they depend upon
fails to build.

Some other best practices:

* Try to avoid installed dependencies to detect changes in the projects
you depend upon early.

* Watch the build results not only of your project but also the
projects that depend on yours to detect backwards cincompatible
changes in your project early.

* If you rename output jars or move files/build directories around,
remember to update the Gump descriptor.

Stefan