You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by co...@jakarta.apache.org on 2004/11/04 03:49:25 UTC

[Jakarta Commons Wiki] Updated: AutomatedIdeas

   Date: 2004-11-03T18:49:24
   Editor: HenriYandell <ba...@apache.org>
   Wiki: Jakarta Commons Wiki
   Page: AutomatedIdeas
   URL: http://wiki.apache.org/jakarta-commons/AutomatedIdeas

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,9 +1,9 @@
-
 Here's a blue sky idea of what I'd like to setup. There are a lot of ties with a classic automated-build system (gump, damagecontrol) but that's not the important part. 
 
  * Fire when change made to CVS; but don't fire too often.
  * Generate and deploy new website for developers, containing many Maven reports (some mentioned in later bullets).
- * Update the build.xml via maven each time.
+ * Update the build.xml via maven each time project.xml is changed, or project.properties?
+ * Update the gump descriptors each time a project.xml is changed.
  * Update a wrapping interface that allows cross-referencing of many of the Maven reports.
  * Generate a jdiff report against the last released version.
  * Use rsync rather than maven site:deploy to save on bandwidth.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org