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

Bug 370812

Summary: Provide support for Generator Extensions to contribute to the EDT Deployment process
Product: z_Archived Reporter: Joseph Vincens <jvincens>
Component: EDTAssignee: Justin Spadea <jspadea>
Status: CLOSED FIXED QA Contact:
Severity: enhancement    
Priority: P1 CC: jspadea, mayunf, svihovec
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: ibmi Extensibility_Runtime
Attachments:
Description Flags
Patch none

Description Joseph Vincens CLA 2012-02-07 07:11:50 EST 
The IBMi feature needs the ability to contribute it's runtime component during deployment.
Comment 1 Yun Feng Ma CLA 2012-02-26 00:46:10 EST 
Created attachment 211629 [details]
Patch

Here is a patch. It will copy org.eclipse.edt.runtime.java.jtopen.jar to WEB-INF/lib if there is one IBMiConnection binding in the eglbld file. Thanks.
Comment 2 Justin Spadea CLA 2012-02-28 10:23:14 EST 
I've made a different fix to CopyJavaRuntimeResourceOperation.java. The requirement for this enhancement was to make any number of generation extensions add to the deployment process. While they can write their own deployment operation, this particular task updated the existing Java runtime copy operation to work with any of the contributed runtime containers.

The way it works is, for any of the EDT Java runtime containers on the Java build path of the source project, they will be copied into the target project. The registered IGenerators are used to get the list of EDTRuntimeContainers, which tell us the bundle IDs to be packaged. Some changes to EDTRuntimeContainer/EDTRuntimeContainerEntry were made to make some extra information public, like the bundle ID.
Comment 3 Joseph Vincens CLA 2012-03-27 10:59:31 EDT 
seems to be implemented