Re: [SrcML] static source code analyzis

[Leif B. <lei...@ma...>]

Hmm, I think the term "plug-in" is a little confusing. With plug-ins I 
mean the plug-ins for the "analyzer platform", which are accesible via 
the API. To use them, we need a "tool", which can be either a single 
java program or an Eclipse plug-in.

> Ant plugin? Ant is a build platform which is comparable to GNU make.
> I don't think it makes sense to plug into that.
What I meant was to create an Ant task to call the analyzer tool 
(written in java for example). Just like you execute the JUnit tests. 
For me it makes sense, because you could run your JUnit tests with 'ant 
test' and your static analysis with 'ant analyze'. What do you think?

> As for an Eclipse plugin this has been planned for a while now. We can
> offer you a book on the subject (Gamma et.al: Contributing to Eclipse)
> in which you can read up on how plugins for Eclipse are created. 
> Basically
> it's a very simple process of writing a special XML file for your 
> plugin.

> The statical analyses per se don't really require Eclipse, so the 
> Eclipse
> integration would rather mean making the complete SrcML Framework 
> available
> within Eclipse (i.e. allowing the current file/project to be parsed). 
> We'll
> have to think of how to get the plugins done easily and still be able 
> to
> run the rest without Eclipse as well.
I would appreciate an Eclipse plug-in for the SrcML project, too. And 
the analyze functions should be part of it. But I think this whole 
plug-in is work for more than one person :-)

Leif Bladt