From 625a6d3cb3e2818125ccc7222ef5a5277a4e183a Mon Sep 17 00:00:00 2001
From: Andrea Aime <andrea.aime@gmail.com>
Date: Sat, 31 Dec 2005 17:31:35 +0000
Subject: [PATCH] Comments on the changed behaviour for association targets
 class lookup

---
 doc/cd-model.xml | 2 ++
 doc/ver.xml      | 5 +++++
 2 files changed, 7 insertions(+)

diff --git a/doc/cd-model.xml b/doc/cd-model.xml
index 1f6f28b..e02b08d 100644
--- a/doc/cd-model.xml
+++ b/doc/cd-model.xml
@@ -51,6 +51,8 @@ to enclose stereotype names.
 These will be automatically enclosed in guillemots.
 Note that a relationship's target class is not implicitly
 defined; it should also be specified using the Java class syntax.
+The target can be specified by simple name, java class lookup rules 
+(imports and visibility) will be used to determine the actual class.
 The following is an example of a relationship
 specification and the resulting UML diagram:
 <table>
diff --git a/doc/ver.xml b/doc/ver.xml
index 5f73dbe..bdb243c 100644
--- a/doc/ver.xml
+++ b/doc/ver.xml
@@ -7,6 +7,11 @@
 <ul>
 <li> Correct the handling of qualified class names following
 the extends keyword (Arnaud Rogues).</li>
+<li> Standard class lookup for association targets. The target can be
+     specified by name without the need to include the full package
+     information, imports and standard visibility rules will be applied
+     to determine the actual class
+</li>
 <li> A <em>views</em> feature provides the ability to specify package-based
 option overrides in UMLOptions like classes,
 and to generate multiple diagrams out of a code base in a single pass.