Nicolas Anquetil-2 wrote:
Hi Alberto,
For the moment, verveineJ does not export this information.
The main reason being that the meta-model does not represent "import" as
an association.
And it would not be that easy to add, because imports are made from a file
(actually, a CompilationUnit) which may contain more than one class.
After that, another difficulty from verveine point of view this time is
that you can import all the classes from a package (import java.io.*) or
import a single method (import static org.junit.Assert.assertEquals).
Yep, your point is absolutely clear.
Nicolas Anquetil-2 wrote:
What you could do, is look at the classes that one class depends on, and
then look at their packages, and if their packages is different from the
initial class' package, you may assume they are imported, ...
That's a good idea. Fortunately I just need the text of the imports, so I
will parse it.
Thank you,
Alberto
--
View this message in context:
http://moose-dev.97923.n3.nabble.com/Classes-and-Namespaces-imported-by-a-J…
Sent from the moose-dev mailing list archive at
Nabble.com.