I'm not certain that this made it out the first time. If it did, I
apologize for the duplicate message.
********************************************************
R a t i o n a l
the e-development company(tm)
Todd Dunnavant
Technical Lead, South Texas District
Office Phone #: (281) 431-8751
Fax Phone #: (281) 431-8791
E-mail address: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Rational's Mission: "To ensure the success of Customers who
depend on software development and deployment."
********************************************************
-----Original Message-----
From: Dunnavant, Todd
Sent: Thursday, June 28, 2001 4:15 PM
To: Rose_Forum (E-mail)
Subject: RE: (ROSE) CURDIR revisited
Anthony,
You most likely are going to need to use a unique path map symbol for each
disconnected directory hierarchy that contains resources which you are
incorporating into your Rose model. Further, you **REALLY** need to define
these path map symbols **BEFORE** you start modeling, so that Rose can
register your resources (controlled units, external doc files, etc) using
the appropriate path map symbol.
If we assume that you have mapped CURDIR to "&", the value of CURDIR changes
dynamically as you touch different controlled units within the model. If
you exercise Rose to create a new controlled unit, or to link an external
file to a model element, CURDIR instantaneously takes on the value of the
directory path to the enclosing (parent) controlled unit. If your new
resource (new controlled unit or external file) is located either within
the same directory as the parent unit, or within a directory that is beneath
the parent unit's directory, Rose commonly will record the path to that new
resource in terms of the parent unit's CURDIR. (There are some complex
niche cases where this will not occur, but let's ignore them for this note.)
However, if your new resource is located neither within the same directory
as the parent unit, nor within a directory that is beneath the parent unit's
directory, Rose normally will do the following:
- record the path using a different path map symbol which has been defined
to represent at least part of the directory path to the new resource. If
multiple such path maps exist, Rose will use the one that maps to the
greatest portion of the new resource's directory path.
- record the path explicitly, if no path map symbol exists that maps to any
portion of the new resource's directory path.
Rational's general recommendation for path maps is as follows:
- define a path map symbol, such as CURDIR = &, that Rose will use to
define links between the model file, lower-level controlled units, and other
linked-in resources, provided that each newly-created (or linked-in)
resource is in either the same directory as its parent controlled unit or a
directory beneath the parent's directory.
- define another path map symbol for each additional directory hierarchy
that contains resources which are linked into the Rose model. These
resources can include documentation files, reusable controlled units, etc.
- all project members should define these same path maps before the
modelling effort begins, so that Rose can register new resources, using the
most appropriate path maps, as those resources are added to the model.
********************************************************
R a t i o n a l
the e-development company(tm)
Todd Dunnavant
Technical Lead, South Texas District
Office Phone #: (281) 431-8751
Fax Phone #: (281) 431-8791
E-mail address: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Rational's Mission: "To ensure the success of Customers who
depend on software development and deployment."
********************************************************
-----Original Message-----
From: Sumpter, Anthony T (N-Intecon) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 28, 2001 2:03 PM
To: Rose_Forum (E-mail)
Subject: (ROSE) CURDIR revisited
Thank you to all who have responded so far...
The answers that we have gotten back are helpful to a point but the
following is a discussion on the problem in a more enlightened way:
We are trying to use the Rose path map variable CURDIR to cause relative
pathing to controlled unit files and external document files. This is
required as we store our rose models and files in a ClearCase VOB on the
UNIX file system and access through UNIX and NT systems through ClearCase
views. Full path names do not work. We assign CURDIR to the value "&" which
should be interpreted as the current directory - usually where the model is
loaded from.
It seems that CURDIR is recorded into the model file when we originally
control a unit from the model . CURDIR is also recorded when adding a
reference to an external file. Examples:
external_doc_path "$CURDIR\\gc\\common\\docs\\foo.h"))
file_name "$CURDIR\\test_unit.cat"
However when we load an existing unit into the another model, the file_name
is recorded as the full path and file name. Example:
file_name
"Z:\\modles\\svc\\interfaces_provided\\foo2.cat"
The above full path was created on NT Rose but will not work on UNIX; Z: is
not valid on UNIX. When running on UNIX the full path created is not valid
on NT.
We probably could, but strongly prefer not to, use different path map
variables for each location of files.
Questions:
When is the value of CURDIR interpreted?
When does it change? When the model is opened? When a controlled unit is
loaded?
Why isn't CURDIR recorded into the model or unit file when we load or import
another, existing controlled unit?
Can we force Rose to always use CURDIR, even when loading a unit?
The only work-around that we seem to be able to use is to edit the Rose .mdl
file and/or unit files and replace the full path with $CURDIR; is there a
better way?
> A. Todd Sumpter
> Lockheed Martin Management & Data Systems
> * 6304 Spine Rd., Boulder, CO 80301
> * 303/581-4472 (work) / 303/581-4268 (fax)
* 877/369-9836 (pager)
* [EMAIL PROTECTED]
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
