Hi Tom, et al.,
Does the solution I committed fulfill your wishes?
BTW: IMHO, it is good to break up the Main.main() of ArgoUML in small public
functions, such as the new initVersion(). E.g. initI18n(), initLAF(), etc.
This will allow the ArgoUML team to modify matters, and ArgoEclipse can call
these functions, instead of copying parts of Main.main().
Regards,
Michiel
----- Original Message -----
From: "Tom Morris" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, May 09, 2007 7:03 PM
Subject: RE: ArgoEclipse Version (Was: Exception Running Argoeclipse (SVN))
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]
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.467 / Virus Database: 269.6.6/794 - Release Date: 8/05/2007
14:23
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
