buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From as...@apache.org
Subject svn commit: r689393 - in /incubator/buildr/trunk/doc: images/project-structure.png pages/projects.textile
Date Wed, 27 Aug 2008 07:18:48 GMT
Author: assaf
Date: Wed Aug 27 00:18:47 2008
New Revision: 689393

URL: http://svn.apache.org/viewvc?rev=689393&view=rev
Log:
Changed directory structure diagram from boring ASCII art to fancy graphics with rounded corners
and gradients!

Added:
    incubator/buildr/trunk/doc/images/project-structure.png
Modified:
    incubator/buildr/trunk/doc/pages/projects.textile

Added: incubator/buildr/trunk/doc/images/project-structure.png
URL: http://svn.apache.org/viewvc/incubator/buildr/trunk/doc/images/project-structure.png?rev=689393&view=auto
==============================================================================
Files incubator/buildr/trunk/doc/images/project-structure.png (added) and incubator/buildr/trunk/doc/images/project-structure.png
Wed Aug 27 00:18:47 2008 differ

Modified: incubator/buildr/trunk/doc/pages/projects.textile
URL: http://svn.apache.org/viewvc/incubator/buildr/trunk/doc/pages/projects.textile?rev=689393&r1=689392&r2=689393&view=diff
==============================================================================
--- incubator/buildr/trunk/doc/pages/projects.textile (original)
+++ incubator/buildr/trunk/doc/pages/projects.textile Wed Aug 27 00:18:47 2008
@@ -71,43 +71,9 @@
 
 When projects grow big, you split them into smaller projects by nesting projects inside each
other.  Each sub-project has a sub-directory under the parent project and follows the same
internal directory structure.  You can, of course, change all of that to suite your needs,
but if you follow these conventions, Buildr will figure all the paths for you.
 
-Going back to the example above, the directory structure looks like this:
+Going back to the example above, the directory structure will look something like this:
 
-{{{
-./buildfile              <- Top of the world (killer-app)
-  |
-  |__ teh-api
-  |   |__ src
-  |   |   |__ main
-  |   |       |__ java   <- Java sources
-  |   |
-  |   |__ target         <- JAR goes here
-  |   |   |__ classes    <- Generated bytecode
-  |   |__ reports        <- From test cases,
-  |       |__ junit      <- like JUnit
-  |
-  |__ teh-impl
-  |   |__ src
-  |   |   |__ main
-  |   |   |   |__ java
-  |   |   |   |__ resources
-  |   |   |__ test
-  |   |       |__ java
-  |   |
-  |   |__ target
-  |   |   |__ classes
-  |   |__ reports
-  |
-  |__ la-web
-  |   |__ src
-  |   |   |__ main
-  |   |       |__ webapp <- Webapp files
-  |   |
-  |   |__ target         <- The WAR goes here
-  |
-  |__ reports 
-      |__ junit          <- For all test cases
-}}}
+p=. !images/project-structure.png!
 
 Notice the @buildfile@ at the top.  That's your project build script, the one Buildr runs.
 



Mime
View raw message