Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 295632 - Java Metamodel discoverer evolution
Summary: Java Metamodel discoverer evolution
Status: CLOSED FIXED
Alias: None
Product: MoDisco
Classification: Modeling
Component: Technologies (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.8.0 M4   Edit
Assignee: Hugo Bruneliere CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 295628
Blocks: 295639
  Show dependency tree
 
Reported: 2009-11-19 13:19 EST by Fabien Giquel CLA
Modified: 2011-05-23 08:57 EDT (History)
4 users (show)

See Also:
fabien.giquel: iplog+

Attachments
Java Metamodel Discoverer evolution (1.05 MB, patch)
2009-11-19 13:19 EST, Fabien Giquel CLA 		fabien.giquel: iplog+
Details | Diff
View All 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 2009-11-19 13:19:27 EST 
Created attachment 152621 [details]
Java Metamodel Discoverer evolution

Hi,

here is a contribution to MoDisco java discoverer, which includes :

- taking in account a Java metamodel evolution (see related bug)
- includes a Java to KDM transformation feature (
- includes byte code analysis (jar/class)
- includes an incremental mode for memory usage optimization
- includes a discovery settings ui

Contributors of this evolution are : Romain DERVAUX and Fabien GIQUEL

The contribution from Romain Dervaux (non committer) exceeds 250 lines of code
: Hugo, can you please initiate some CQ for the whole content of the evolution
?

Thanks,
Fabien.
Comment 1 Romain Dervaux CLA 2009-11-19 14:55:42 EST 
1. I, DERVAUX romain, and others contributors listed in this bug, authored 100%
of the content
2. I have the rights to donate the content to Eclipse under the EPL
3. I have already provided the filled Employer Consent Forms to the Foundation

Romain DERVAUX
Comment 2 Hugo Bruneliere CLA 2009-11-20 05:06:25 EST 
Hi Fabien,

Thanks for your contribution. 

As this contribution depends from the one in Bug #295628, could you apply the patch provided from this Bug #295628, then commit the upgraded version of the plug-in and finally validate the process by closing/fixing it? 

I will create the CQ for the current bug (#295632) afterwards.

Best regards,

Hugo
Comment 3 Fabien Giquel CLA 2009-11-20 06:36:46 EST 
Hi Hugo,

yes it is logical to apply and close Bug #295628 before processing this one.

However I did not, because applying #295628 will modify the 'org.eclipse.gmt.modisco.java' component (0.6.0 -> 0.7.0) and so the current 'org.eclipse.gmt.modisco.java.discoverer' (0.6.0) will not work anymore until the #295632 bug would be applied (depends on CQ processing time).

i.e. java components from nightly/integration builds & update sites, would not work anymore during this period.

Is it not possible to initiate CQ for the #295632 even if #295268 is not processed ? Or do you see a better way to follow ?

Fabien.
Comment 4 Hugo Bruneliere CLA 2009-11-23 04:54:21 EST 
Hi Fabien,

I've just created a CQ for this bug attaching the provided patch.
I will keep you informed of the IP validation progress.

Best regards,

Hugo
Comment 5 Hugo Bruneliere CLA 2009-11-27 08:11:13 EST 
Hi Fabien,

This patch has been sucessfully validated.
You can now commit the various changes.

Best regards,

Hugo