> -----Original Message-----
> From: Norris, Davyd [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, November 18, 2000 7:47 AM
> 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.
Using a text format is great plus but why not using XML now? (yes I know of XMI but we don't want to export data, we want to *version* it). The Rose petal format is not less proprietary because it's text; the format is not public, not safely backward-compatible but it does "encourage" some third-party vendors to take shortcuts not using the REI (probably because the REI's too slow).
The VisualAge repository does have a nice Rose integration, but I wouldn't call VAJ open. You still need the EMSRV, it has a limited Java-only API (not covering the EJB objects afaik) and the integration is using the aged SCCI interface in the wait for a ClearCase WebDAV implementation.
> > 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.
And I though the latest ClearCase integration was good because it went outside the SCC API ;-)
But it's no exactly invisible for a typical Rose user, Rose could do much better if Rational added a default file mapping tool for controlled units and external documents (including SoDA reports). This and auto-computed relative file references would assist our Rose users a lot.
Sten Rosendahl ([EMAIL PROTECTED])
IMI Corp.
