Home » Archived » Buckminster » Emma Update
| |
| Re: Emma Update [message #986103 is a reply to message #986086] |
Sun, 18 November 2012 21:53   |
|
The problem here is that since emma is a third-party component, we
cannot just upgrade. First we must submit the new version for review byt
the Eclipse EMO and if it has any additional dependencies (such as
jacoco?) those too must be reviewed. Nobody has had any time to go
through that process with emma just yet.
- thomas
On 2012-11-18 18:21, Bernard SARTER wrote:
> Hello,
>
> I faced the same problem at the beginning of the year, and opened an
> issue in BugZilla:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=368042
>
> I also enclosed a simple patch to the BugZilla, that's working fine for
> me so far (allows to use a recent version of JaCoCo, compatible with
> Java 7), but nobody seems to really work on a proper fix ...
>
> Might be you could vote for the issue to increase its ranking ...
>
> Regards,
> Bernard.
>
|
|
|
| Re: Emma Update [message #986104 is a reply to message #986103] |
Sun, 18 November 2012 22:01 |
|
I see that there's an update site where EclEmma is published nowadays.
That could simplify things a bit. What we can do right now is to could
move our headless emma feature to the external site like we already do
with subclipse and subversive.
- thomas
On 2012-11-18 22:53, Thomas Hallgren wrote:
> The problem here is that since emma is a third-party component, we
> cannot just upgrade. First we must submit the new version for review byt
> the Eclipse EMO and if it has any additional dependencies (such as
> jacoco?) those too must be reviewed. Nobody has had any time to go
> through that process with emma just yet.
>
> - thomas
>
>
>
> On 2012-11-18 18:21, Bernard SARTER wrote:
>> Hello,
>>
>> I faced the same problem at the beginning of the year, and opened an
>> issue in BugZilla:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=368042
>>
>> I also enclosed a simple patch to the BugZilla, that's working fine for
>> me so far (allows to use a recent version of JaCoCo, compatible with
>> Java 7), but nobody seems to really work on a proper fix ...
>>
>> Might be you could vote for the issue to increase its ranking ...
>>
>> Regards,
>> Bernard.
>>
>
|
|
|
| Re: Emma Update [message #986116 is a reply to message #986104] |
Sun, 18 November 2012 23:56 |
|
Bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=368042 has been now
fixed and the Emma feature has found a new home at our external update site:
http://download.cloudsmith.com/buckminster/external-4.2
The emma version is now 2.2.0. Please try it out.
- thomas
On 2012-11-18 23:01, Thomas Hallgren wrote:
> I see that there's an update site where EclEmma is published nowadays.
> That could simplify things a bit. What we can do right now is to could
> move our headless emma feature to the external site like we already do
> with subclipse and subversive.
>
> - thomas
>
>
> On 2012-11-18 22:53, Thomas Hallgren wrote:
>> The problem here is that since emma is a third-party component, we
>> cannot just upgrade. First we must submit the new version for review byt
>> the Eclipse EMO and if it has any additional dependencies (such as
>> jacoco?) those too must be reviewed. Nobody has had any time to go
>> through that process with emma just yet.
>>
>> - thomas
>>
>>
>>
>> On 2012-11-18 18:21, Bernard SARTER wrote:
>>> Hello,
>>>
>>> I faced the same problem at the beginning of the year, and opened an
>>> issue in BugZilla:
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=368042
>>>
>>> I also enclosed a simple patch to the BugZilla, that's working fine for
>>> me so far (allows to use a recent version of JaCoCo, compatible with
>>> Java 7), but nobody seems to really work on a proper fix ...
>>>
>>> Might be you could vote for the issue to increase its ranking ...
>>>
>>> Regards,
>>> Bernard.
>>>
>>
>
|
|
| | | | |
| Re: Emma Update [message #1068132 is a reply to message #1067932] |
Fri, 12 July 2013 10:44 |
|
On 07/11/2013 12:39 PM, Flavio Donze wrote:
> Hi Lorenzo
>
> Thanks for your hint!
>
> I had to change the emma command from:
> emma -l '/ch.scodi.server.test.site/ScodiServerTest.launch' -o
> '${WORKSPACE}/output/junit_result.xml' --xml
> '${WORKSPACE}/output/coverage_report.xml' --flatXML --stdout
> '${WORKSPACE}/output/stdout.txt' --stderr '${WORKSPACE}/output/stderr.txt'
>
> to
>
> emma -l '/ch.scodi.server.test.site/ScodiServerTest.launch' -o
> '${WORKSPACE}/output/junit_result.xml' --exec
> '${WORKSPACE}/output/jacoco.exec' --flatXML --stdout
> '${WORKSPACE}/output/stdout.txt' --stderr '${WORKSPACE}/output/stderr.txt'
>
> and now it works!
Right! I forgot to mention that the plugin supports only the exec format :)
The sad news is that, as far as I understand, the Jenkins Jacoco plugin
requires additional configurations for exclusions of sources/classes
etc. (see also this
https://groups.google.com/forum/#!topic/jenkins-jacoco-plugin-mailing-list/MRbOzqWJ580
).
That's a pity, since in the EclEmma launch configuration you can already
state exclusions (at source folders level), and then you need to
configure exclusions again (but not at source folders level) so that the
plugin creates the report according to your needs... Especially for
Xtext projects you usually want to exclude the generated sources;
excluding them in the launch configuration is easy (you just exclude
generated source folders, e.g., src-gen), but for the plugin you need to
specify exclusions at package levels... it takes some time to get it
right the first time, but then it works :)
cheers
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
Goto Forum:
Current Time: Fri Apr 19 23:29:14 GMT 2024
Powered by FUDForum. Page generated in 0.03496 seconds |
] 
Search
Help
Register
Login
Home
