beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers" <>
Subject Re: svn depot reference [was: Fwd: Trivial Update of "For Beehive Developers" by CarlinRogers]
Date Fri, 11 Aug 2006 20:54:43 GMT
Ooooh, excellent catch. Thanks Eddie. I'll nuke that now.

Any other have thoughts about the addition of the SVN information or links
on the wiki page as help devs? We may not really need some of the explicit
command information so I can remove some of that. Input?

Kind regards,

On 8/11/06, Eddie O'Neil <> wrote:
> Carlin--
>   Hey -- good to have new content on the wiki.  One one of the URLs
> below, the ASF infrastructure team has asked projects to avoid
> references to the "dynamic" view of the SVN repository because of the
> load that generates on the servers.  Static references of the form:
> are fine, but the ones that go through the CGI script are lots more
> expensive.
>   So, it'd be great if we could remove that link.  :)
> Eddie
> ---------- Forwarded message ----------
> From: Apache Wiki <>
> Date: Aug 11, 2006 1:29 PM
> Subject: [Beehive Wiki] Trivial Update of "For Beehive Developers" by
> CarlinRogers
> To:
> Dear Wiki user,
> You have subscribed to a wiki page or wiki category on "Beehive Wiki"
> for change notification.
> The following page has been changed by CarlinRogers:
> ------------------------------------------------------------------------------
>      5. examining history: svn log
>   }}}
>   Note that svn treats directories as first class objects, so you need
> to "svn add" them.
> +
> + No authentication is needed for read-only access to the
> repositories. However, you must be a committer and authenticate using
> your Apache userid/svn password when using svn to do any modifying
> operations. Set your svn password according to the instructions at
>   = Build Conventions =
>   The Beehive build is structured such that the Beehive components are
> peers and have a location in which to reference shared components.
> Artifacts of these shared components are defined as properties in the
> `/beehive-imports.xml` file, which can be included by any downstream
> Ant build file.  Some of these artifacts include references to the
> XMLBeans JAR, the Servlet and JSP API JARs, and the JUnit JAR.  The
> motivation behind this is to minimize the number of properties used to
> refer to the same resource, and when possible, these common properties
> should be used in component projects.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message