Update of /cvsroot/metamorphosis/ruper2/src/documentation/content/xdocs
In directory sc8-pr-cvs1:/tmp/cvs-serv25787/src/documentation/content/xdocs
Modified Files:
tabs.xml index.xml
Log Message:
Some doc tweaks...
Index: tabs.xml
===================================================================
RCS file: /cvsroot/metamorphosis/ruper2/src/documentation/content/xdocs/tabs.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** tabs.xml 1 Oct 2003 21:55:55 -0000 1.1
--- tabs.xml 14 Oct 2003 20:48:07 -0000 1.2
***************
*** 1,14 ****
<?xml version="1.0" encoding="UTF-8"?>
! <!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN" "tab-cocoon-v10.dtd">
! <tabs software="Krysalis Ruper"
! title="Krysalis Ruper"
! copyright="2002-@year@ Krysalis Project"
! xmlns:xlink="http://www.w3.org/1999/xlink">
<tab label="Home" dir=""/>
<tab label="Tools" dir="tool"/>
<tab label="Ant Tasks" dir="ant"/>
- <tab label="AntLib" dir="antlib"/>
<tab label="Eclipse" dir="eclipse" />
! </tabs>
--- 1,13 ----
<?xml version="1.0" encoding="UTF-8"?>
! <!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN" "tab-cocoon-v10.dtd">
! <tabs software="Krysalis Ruper"
! title="Krysalis Ruper"
! copyright="2002-@year@ Krysalis Project"
! xmlns:xlink="http://www.w3.org/1999/xlink">
<tab label="Home" dir=""/>
<tab label="Tools" dir="tool"/>
<tab label="Ant Tasks" dir="ant"/>
<tab label="Eclipse" dir="eclipse" />
! </tabs>
Index: index.xml
===================================================================
RCS file: /cvsroot/metamorphosis/ruper2/src/documentation/content/xdocs/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** index.xml 14 Oct 2003 17:56:21 -0000 1.2
--- index.xml 14 Oct 2003 20:48:07 -0000 1.3
***************
*** 12,16 ****
<p>Say you have a build script that uses releases of certain jars, e.g. junit.jar or commons-logging.jar, you could ask Ruper to get the latest <strong>release</strong> of these, and store it in your <code>./lib</code> directory.
Alternatively, you could create a shared <code>$HOME/jars</code> directory (say) so all your build scripts share the latest release.</p>
! <p>For more information, ask the <link href="http://krysalis.org/wiki/Ruper">Wiki</link>.</p>
</section>
</body>
--- 12,41 ----
<p>Say you have a build script that uses releases of certain jars, e.g. junit.jar or commons-logging.jar, you could ask Ruper to get the latest <strong>release</strong> of these, and store it in your <code>./lib</code> directory.
Alternatively, you could create a shared <code>$HOME/jars</code> directory (say) so all your build scripts share the latest release.</p>
!
! <p>For more information, ask the <fork href="http://krysalis.org/wiki/Ruper2">Wiki</fork> and also as it about history on <fork href="http://krysalis.org/wiki/Ruper">Ruper1</fork>.</p>
! </section>
!
! <section><title>Why Ruper was created...</title>
! <p>Krysalis-Ruper was developed as a middle ground between <fork href="http://ant.apache.org/manual/CoreTasks/get.html">Ant <get</fork> (to download a certain 'stale' version of a jar) and the relative chaos of <fork href="http://jakarta.apache.org/gump">Jakarta Gump</fork> (which gets/build the absolute latest ever time).
! </p>
! <source>
! An example of a 'potentially stale' update (version is hard coded.)
!
! <get src="http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.jar"
! dest="${lib}/commons-logging.jar"
! usetimestamp="true"
! verbose="true"/>
! </source>
! <p>
! Krysalis Ruper performs as a 'negotiation' between the (remote) repository populators and the (local) builder.
! For example, a new 'release candiate' of a JAR could be published.
! Typically Ruper would download it, but it could be asked to not do so, and only download 'release' level code.
! </p>
!
! <p>Ruper <strong>trusts the repository manager, but answers to the builder</strong> so allows a blend.</p>
!
! <p>Krysalis-Ruper helps reduce <fork href="http://krysalis.org/version/jar-hell">JAR HELL</fork> by reducing stagnant code compiling/testing.
! The more projects that work of "out of date" code, the more chance that combining those projects in a single runtime environment
! will suffer irrepairable jar-hell through incompatibilities.</p>
</section>
</body>
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.