> But maybe, on second thought, we should keep the ArgoUML 
> version accessable 
> to ArgoEclipse, even if you have your own version - like 
> "ArgoEclipse V0.5 
> based on ArgoUML V0.25.3".

It's definitely useful, at least from a user point of view, to have the core
ArgoUML version available.  All of the features and bugs in the ArgoUML bug
database are tied to this version number.  

We can probably work around this by incorporating it somewhere into our own
version information during the build process, but I would have thought the
host ArgoUML version would be useful for any plugin modules too.  The
version of ArgoUML that they were built against isn't necessarily the same
as the one that they're going to be running with at some later point.

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to