You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beehive.apache.org by Apache Wiki <wi...@apache.org> on 2006/08/11 22:16:31 UTC

[Beehive Wiki] Trivial Update of "For Beehive Developers" by CarlinRogers

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:
http://wiki.apache.org/beehive/For_Beehive_Developers

The comment on the change is:
adding some additional information about svn

------------------------------------------------------------------------------
    svn checkout https://svn.apache.org/repos/asf/beehive/trunk
  }}}
   * follow the instructions in [http://svn.apache.org/repos/asf/beehive/trunk/BUILDING.txt BUILDING.txt]
+ 
+ = More about Subversion and the ASF Source Code Repository =
+ Additional references:
+  * [http://www.apache.org/dev/version-control.html The Apache Software Foundation Source Code Repository]
+  * [http://svn.apache.org/viewcvs.cgi/beehive/?root=Apache-SVN Web-Browsable View of the Beehive subversion repository at Apache]
+  * [http://svnbook.red-bean.com svn online manual]
+  * [http://osdir.com/Article203.phtml intro to svn for cvs users]
+ Example operations:
+ {{{
+    1. adding new files: svn add
+    2. editing existing files -- just do it, svn doesn't require an "open" or "edit" command.
+    3. syncing to repository changes: svn update
+    4. submitting changes: svn commit
+    5. examining history: svn log 
+ }}}
+ Note that svn treats directories as first class objects, so you need to "svn add" them.
  
  = 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.