Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 256323 - [build][discovery] add EMF components (core and net4j) to ECF build
Summary: [build][discovery] add EMF components (core and net4j) to ECF build
Status: RESOLVED FIXED
Alias: None
Product: ECF
Classification: RT
Component: ecf.core (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Markus Kuppe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 256603
  Show dependency tree
 
Reported: 2008-11-24 15:05 EST by Scott Lewis CLA
Modified: 2008-12-18 11:26 EST (History)
2 users (show)

See Also:

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 Scott Lewis CLA 2008-11-24 15:05:57 EST 
We will soon have two ECF components that are dependent upon parts of EMF:

1) Discovery UI contributed by Markus Kuppe (dependent upon EMF core and perhaps EMF/SDO serialization)

2) Net4j provider (dependent upon Net4j)

In order to be able to build and deploy the discovery UI and the net4j provider we will need to add the incorporation of the required EMF core and Net4j plugins...either by building them ourselves, or taking built versions and adding them to our own build.
Comment 1 Markus Kuppe CLA 2008-11-25 03:29:29 EST 
(In reply to comment #0)
> We will soon have two ECF components that are dependent upon parts of EMF:
> 
> 1) Discovery UI contributed by Markus Kuppe (dependent upon EMF core and
> perhaps EMF/SDO serialization)

Deps are:

org.eclipse.emf,
org.eclipse.emf.core,
org.eclipse.emf.common.ui,
org.eclipse.emf.common,
org.eclipse.emf.edit.ui,
org.eclipse.emf.edit,

>= 2.4

> 2) Net4j provider (dependent upon Net4j)
> 
> In order to be able to build and deploy the discovery UI and the net4j provider
> we will need to add the incorporation of the required EMF core and Net4j
> plugins...either by building them ourselves, or taking built versions and
> adding them to our own build.

+1 for reusing EMF builds instead of building on our own.
Comment 2 Markus Kuppe CLA 2008-12-10 14:07:35 EST 
Hi Ted, Scott,

if I'd want to add EMF to our build, I assume I simply extract it to:

build.environment.properties:     eclipse.home = /opt/eclipse3.4.1/eclipse

I target EMF runtime 2.4.1 [1]. The latest stable EMF version.

[1] http://www.eclipse.org/modeling/download.php?file=/modeling/emf/emf/downloads/drops/2.4.1/R200808251517/emf-runtime-2.4.1.zip
Comment 3 Markus Kuppe CLA 2008-12-12 03:19:04 EST 
I've extracted EMF runtime 2.4.1 into /opt/eclipse-3.4.1/dropins on ecf2.
Comment 4 Markus Kuppe CLA 2008-12-18 11:26:19 EST 
Marking as fixed