Until this feature is implemented, does anyone have ideas for workarounds? I was thinking of something along the lines of defining a "Run Application" to run emma or emmarun, and passing the appropriate info as parameters. However, I couldn't think how this would be possible (I got stuck on how to specify the right classpath). Has anyone else tried this?
Thanks,
Chad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As a quick thought, I usually let Eclipse use a default location for compiled classes (./out or ./bin). You can then run EMMA as an external tool and configure it to be run from the project dir and use a "-cp out" option, etc.
Also, what about running EMMA via ANT tasks from Eclipse?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On the first option, what about all the dependent jars in my lib folder? Wouldn't I have to explicitly add them to the -cp option too? That's the part that seems like a pain.
On the ANT task option, that is workable, but then you lose the benefit of the nice integrated GUI JUnit test runner.
Of course, I did just ask for a "workaround" so I shouldn't be so demanding :)
Thanks for the response,
Chad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there a plugin for Eclipse ?
Not at the moment. Feature request added (https://sourceforge.net/tracker/index.php?func=detail&aid=962001&group_id=108932&atid=651900)
Until this feature is implemented, does anyone have ideas for workarounds? I was thinking of something along the lines of defining a "Run Application" to run emma or emmarun, and passing the appropriate info as parameters. However, I couldn't think how this would be possible (I got stuck on how to specify the right classpath). Has anyone else tried this?
Thanks,
Chad
As a quick thought, I usually let Eclipse use a default location for compiled classes (./out or ./bin). You can then run EMMA as an external tool and configure it to be run from the project dir and use a "-cp out" option, etc.
Also, what about running EMMA via ANT tasks from Eclipse?
On the first option, what about all the dependent jars in my lib folder? Wouldn't I have to explicitly add them to the -cp option too? That's the part that seems like a pain.
On the ANT task option, that is workable, but then you lose the benefit of the nice integrated GUI JUnit test runner.
Of course, I did just ask for a "workaround" so I shouldn't be so demanding :)
Thanks for the response,
Chad