Update of /cvsroot/metamorphosis/krysalis-version/src/documentation/content/xdocs/ant
In directory sc8-pr-cvs1:/tmp/cvs-serv28886/src/documentation/content/xdocs/ant
Modified Files:
overview.xml faq.xml
Log Message:
Document updates for ant tasks
Index: overview.xml
===================================================================
RCS file: /cvsroot/metamorphosis/krysalis-version/src/documentation/content/xdocs/ant/overview.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** overview.xml 12 Feb 2003 20:51:45 -0000 1.1
--- overview.xml 12 Feb 2003 22:45:00 -0000 1.2
***************
*** 16,25 ****
</section>
<section><title>Management Tasks</title>
! <p>Management tasks help you manage the versions and constraints you generate within your own developments.
</p>
</section>
<section><title>Runtime Tasks</title>
! <p>Runtime tasks help you work with the version you depend upon within your own developments.
! </p>
</section>
</body>
--- 16,34 ----
</section>
<section><title>Management Tasks</title>
! <p>Management tasks help you manage the versions and constraints you generate within your own developments.
! These are "branded" into the code by means of generating source code into your source directory <strong>(dest)</strong>.
! Creating <strong><code>{your.stuff.package}.version.Version.class</code></strong> so as not to clash with your code,
! (and <strong>overWrite</strong> defaulting to false to be doubly sure).
! You then compile and distribute this class with your JAR.
</p>
+ <note>This <code>Version.class</code> is not dependent upon <strong>Krysalis Version</strong> or anything but the standard JDK class, with any recent JDK.
+ This class has no ties to other classes in your package, nor others with ties to it. It is as benign a class as one could imagine.
+ Branding version information into your package is riskless, and benifit loaden.</note>
</section>
<section><title>Runtime Tasks</title>
! <p>Runtime tasks help you work with the version you depend upon within your own developments.</p>
! <p>Runtime tasks 'introspect' your runtime environment (via classloaders) and locates classes.
! If asked a question for a given package (e.g. <code>"personal.my.stuff"</code>) it looks for <code>personal.my.stuff.version.Version</code> and introspects/loads.</p>
! <p>Runtime tasks determine the versions within the environment and allow you to perform actions, i.e. set properties <link href="available.html">(version-available)</link> or fail <link href="constrain.html">(version-constrain)</link></p>
</section>
</body>
Index: faq.xml
===================================================================
RCS file: /cvsroot/metamorphosis/krysalis-version/src/documentation/content/xdocs/ant/faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** faq.xml 12 Feb 2003 20:51:47 -0000 1.1
--- faq.xml 12 Feb 2003 22:45:00 -0000 1.2
***************
*** 13,17 ****
<section><title>FAQ</title>
<section><title>How do I define these tasks to ant?</title></section>
! <section><title>How do I ...</title></section>
</section>
</body>
--- 13,18 ----
<section><title>FAQ</title>
<section><title>How do I define these tasks to ant?</title></section>
! <section><title>How does this differ than a Manifest.mf ...</title></section>
! <section><title>How does this differ from naming the JAR to include the version?</title></section>
</section>
</body>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
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.