Hi Arne,
See below for more comments. It's nice to know that my explanation at least
made sense!
> -----Original Message-----
> From: Arne G. Styve [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, 18 November 2000 1:49 AM
[...]
>
> What you say about " - there was no versioning of model info"
> when using a
> DB back end I find rather strange.
You had to build it into your product and many of them did not. If they did,
it was at the wrong level (right down at the attribute/operation/element
level, rather than across groups of elements that had to remain consistent
with each other)
[...]
> earlier (which by the time I used it was called ObjectTeam (no, not
> ObjetcTime)) had excelent versioning control both on the
> sourcefiles it
> generated from the then OMT-models, and the model-elements
> themselves. And
> that tool used a standard SQL Oracle DB as a back end.
Interesting. Cayenne, then ObjectTeam (, then Sterling Cool:Jex, now CA-??)
used to use an object database when I used it. I believe it was ObjectStore,
since it blew my version to bits when I installed it!!
[...]
> However, why don't Rational provide versioning as standard in
> Rose ? Why
> only rely on an "external" tool ?
One of the other considerations Rational had was that you needed to enable
the team, so all your project artefacts should be able to be stored and
versioned alongside each other in the same repository. This meant that Rose
models should be thought of like source and other documents, making an open
versioning model mandatory.
Going proprietary is not an option here - another reason against DB
repositories. One example - early versions of Visual Age for Java were
lovely for the coder role to work with, but very hard for anyone else since
they used a closed repository that versioned the code well but not anything
else. Now they have opened up their back end and we have a nice tight
integration.
> One could have imagined a
> solution where
> say ClearCase was completely integrated (and for that sake,
> invisible for
> the user) with Rose,
ClearCase _is_ completely integrated with Rose, as is any SCC compliant
version control system. We also provide the REI to do it yourself as well as
a standard text-based hook system for command line driven CM tools. I once
integrated CVS running on DEC Unix with Rose on NT. Folks would store their
models on a SAMBA mounted drive and Rose would check in and out using rshell
commands!! I was told by the client that it was 'transparent'.
[...]
> Versioning tools too, but since you own a tool like
> ClearCase, why not ship
> it with Rose in the first place ?
OK, OK, OK... Just for you Arne I have asked our team to whip something up
pronto.
Have a look on our Web site for the new features in the next Suites release
:-)
Regards,
Dave.
--
Davyd Norris - Consultant
Regional Services Organisation (Asia Pacific)
Rational Software
Sydney, Australia.
Phone: +61 2 9419 0100
Fax : +61 2 9419 0160
HDesk: +61 2 9419 0111
--
************************************************************************
* 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
*
*************************************************************************
