Hello Rick!
To my knownledge there is only one tool that understands the @stereotype tag
when reading the java code and does something meaningful with it and it is
ArgoUML itself when doing java source imports. I am not sure if it still
works.
The idea is that classes, methods, and member objects in the code, when
imported automatically get the correct stereotype set in the model.
In the argouml source code I think it is only used for singleton classes.
/Linus
2008/1/14, Rick van der Zwet <[EMAIL PROTECTED]>:
>
> On 1/14/08 8:34 PM, Tom Morris wrote:
> > Answers to your questions are inline below:
> >
> > On Jan 13, 2008 7:29 PM, Rick van der Zwet <[EMAIL PROTECTED]>
> wrote:
> >> I do have a few questions however:
> >> * @stereotype tag is heavenly used throughout the code, although this
> is
> >> a valid tag at the eclipse doc generator, it will produce many,many
> >> warnings in a non eclipse environment.
> >> Any idea how to get rid of this without starting to use eclipse?
> >
> > I count less than 50 occurrences, which I don't consider very many
> > considering the number of classes that we have. Do the warnings occur
> > with our standard Ant build file?
>
> 'many,many' was indeed a bit vague, 43 warnings is the correct one.
> ~/src/argouml/src_new $ sh build.sh javadocs | grep -c '@stereotype'
> 43
>
> >> * During the init? of javadocs I get a massive amount of warnings about
> >> packages which does not exist (like [1]), how to get around this
> >> warnings, as google is not very helpful providing a answer :-(
> >>
> >> [1]
> >>
> [javadoc]/src/model-mdr/src/org/argouml/model/mdr/ActivityGraphsFactoryMDRImpl.java:30:
> >> package org.omg.uml.behavioralelements.activitygraphs does not exist
> >> [javadoc] import
> org.omg.uml.behavioralelements.activitygraphs.ActionState;
> >
> > The code for the org.omg.uml.* packages is generated at build time
> > from the UML 1.4 metamodel by the Ant build. The MDR build does this
> > is invoked from the main ArgoUML Ant build. Are you using our build
> > process?
>
> The warnings are not generated during build time, but during the init of
> javadocs. I am using the way described in Readme.txt,
> argouml/src_new $ sh build.sh javadocs
>
> /Rick
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
