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

Bug 264821

Summary: Update the build system
Product: z_Archived Reporter: Yves YANG <yves.yang>
Component: VEAssignee: Nick Boldt <nboldt>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse, webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:

Description Yves YANG CLA 2009-02-13 04:51:27 EST
VE is out of date since more than 2 years. I have faced a problem of build configuration, which is not compatible with current one. To revive VE, the update is critical.
Comment 1 Nick Boldt CLA 2009-02-22 23:11:10 EST
To facilitate this, I need three things:

a) Please list which feature(s) you intend to package

b) Please define how best to package VE for community consumption. I'm thinking zips of SDK, runtime, examples (if applicable) and JUnit 3 tests (if present), along with a p2 repo / update site.

c) I will also require committer access to the CVS repo, and group write permission in ~/downloads/tools/ve/ on dev.eclipse.org. This last one will require PMC/PL approval, and that this bug be assigned to webmaster@eclipse.org for action.
Comment 2 Nick Boldt CLA 2009-02-22 23:14:02 EST
I also need some basic details, like:

Eclipse version we're targeting (assume Eclipse 3.4+)
JVM version (assume 5.0+)
Runtime requirements (assume we only need Eclipse 3.4+ and EMF 2.4+)

Comment 3 Yves YANG CLA 2009-02-23 11:44:38 EST
(In reply to comment #1)
> To facilitate this, I need three things:
> a) Please list which feature(s) you intend to package

VE depends on: JEM plugins, which are moved in the WTP.  

So we need to include only the following plugins in the feature: 
   org.eclipse.ve.jfc
   org.eclipse.ve.propertysheet
   org.eclipse.ve.swt
   org.eclipse.ve.cde
   org.eclipse.ve.java.core
   org.eclipse.ve.doc

You can reference our update site for runtime only:
    http://update.soyatec.org/Ganymede/ve/1.4

> b) Please define how best to package VE for community consumption. I'm thinking
> zips of SDK, runtime, examples (if applicable) and JUnit 3 tests (if present),
> along with a p2 repo / update site.

I think we provide the zip for SDK and runtime, and two corresponding categories in eclipse update  

> c) I will also require committer access to the CVS repo, and group write
> permission in ~/downloads/tools/ve/ on dev.eclipse.org. This last one will
> require PMC/PL approval, and that this bug be assigned to webmaster@eclipse.org
> for action.

Comment 4 Yves YANG CLA 2009-02-23 11:46:53 EST
(In reply to comment #2)
> I also need some basic details, like:
> Eclipse version we're targeting (assume Eclipse 3.4+)

Yes

> JVM version (assume 5.0+)

Right. 

http://wiki.eclipse.org/VE/Update

> Runtime requirements (assume we only need Eclipse 3.4+ and EMF 2.4+)

Comment 5 Nick Boldt CLA 2009-04-04 04:55:01 EDT
Moving work to bug 270849.

*** This bug has been marked as a duplicate of bug 270849 ***