Moose
Moose copied to clipboard
moosetechnology
Moose Book : ArgoUML source no longer downloadable
I don't know if this is the right place to report this issue.
The Moose Book uses ArgoUML 0.3.4 as an example, and offers a link to download it.
The tigris.org website says it is being decommissioned, but the source can still be downloaded from https://web.archive.org/web/20161118173704/http://argouml-downloads.tigris.org/nonav/argouml-0.34/ArgoUML-0.34-src.zip
Perhaps the link should be updated to that, or to some other destination.
And https://web.archive.org/web/20161118173429/http://argouml-downloads.tigris.org/nonav/argouml-0.34/ArgoUML-0.34-libs.zip
I downloaded ArgoUML source recently. I can put it on Github and we will redirect to it.
I have been checking a bit online. I have find that argouml migrated to github pages. The repositories have been migrated to git repositories https://github.com/argouml-tigris-org/argouml What i think we should do is to update the book and to have a script to download the project from git
I have done a test over the version downloaded from git.
git clone https://github.com/argouml-tigris-org/argouml.git cd argouml "path.to\VerveineJ\verveinej.bat" -o "path.to\Model\Argol.mse" -anchor assoc -alllocals .
And it works fine
Ok. I but don't know who have the right to modify the book
Le ven. 25 sept. 2020 à 11:46, Santiago Bragagnolo [email protected] a écrit :
I have done a test over the version downloaded from git.
git clone https://github.com/argouml-tigris-org/argouml.git cd argouml "path.to\VerveineJ\verveinej.bat" -o "path.to\Model\Argol.mse" -anchor assoc -alllocals .
And it works fine
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/moosetechnology/Moose/issues/2226#issuecomment-698835164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7H2S2EW27CDTWLVOTKHY3SHRRILANCNFSM4MXX7ICA .
I am glad to see it has a home on github, and seems to be (moderately) active. I have a soft spot for that tool, from years back. I still like the critic-based approach. And am currently pursuing it in an LSP context.
