Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344257

Summary:	[Java Discovery] execution time benchmark should be registered as one discoverer
Product:	[Modeling] MoDisco	Reporter:	Fabien Giquel <fabien.giquel>
Component:	Technologies	Assignee:	Nicolas Bros <nicolas.bros>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P1	CC:	gdupe, hugo.bruneliere, modisco.web-inbox, nicolas.bros
Version:	0.9.0	Flags:	nicolas.bros: indigo+
Target Milestone:	0.9.0 RC1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Fabien Giquel

2011-04-29 07:54:18 EDT

The action "Discovery->Actions->Java Benchmark->Benchmark Discovery Time Excecution" should be implemented and declared as one discoverer (menu "Discovery->Discoverer->Java Benchmark->") just as the other Java benchmarks discoverers.

Comment 1 Nicolas Bros

2011-04-29 11:03:54 EDT

Note: this will require an evolution of the discovery framework to handle multiple selection.

Comment 2 Gregoire Dupe

2011-05-02 11:43:00 EDT

Hello,

The multi-selection of the source elements is not required for this discover which is dedicated to the EMF Facet users. To be able to launch a benchmark using a text file which contains the list of the project to use during the benchmark, will be enough.

Regards,
Gregoire Dupe

Comment 3 Nicolas Bros

2011-05-16 11:41:36 EDT

In revision 4400 I've removed the action (asked by Gregoire), and added the number of iterations as a discoverer parameter.

Comment 4 Hugo Bruneliere

2011-08-18 08:19:53 EDT

Upgrade done.