Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344257 - [Java Discovery] execution time benchmark should be registered as one discoverer
Summary: [Java Discovery] execution time benchmark should be registered as one discoverer
Status: CLOSED FIXED
Alias: None
Product: MoDisco
Classification: Modeling
Component: Technologies (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: 0.9.0 RC1   Edit
Assignee: Nicolas Bros CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-29 07:54 EDT by Fabien Giquel CLA
Modified: 2011-08-18 08:19 EDT (History)
4 users (show)

See Also:
nicolas.bros: indigo+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Fabien Giquel CLA 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 CLA 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 CLA 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 CLA 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 CLA 2011-08-18 08:19:53 EDT 
Upgrade done.