| Summary: | Update build process to transform generated runtime classes with SMAPs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Justin Spadea <jspadea> | ||||
| Component: | EDT | Assignee: | Justin Spadea <jspadea> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | xiaobinc | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Justin Spadea
I've added the following files to each of the four Java runtime projects: build/transformer.jar build/customBuildCallbacks.xml transformer.jar is built from the org.eclipse.edt.debug.core project and contains a main class that runs a transformation recursively on a directory for SMAPs. customBuildCallbacks.xml kicks this process off after the project is compiled. Hi Justin, I am writing test scenario for this enhancement. I am not familiar with this enhancement. Could you give me some basic knowledge for this enhancement and how to test this? Created attachment 217543 [details]
Class file containing SMAP data
The easiest way to check it is to open up the Java runtime plug-ins from the build, and for the files that have corresponding *.eglsmap files, open up the .class files in a text editor, scroll to the end of the binary data, and the SMAP contents should be displayed. See the attached screenshot with the SMAP file on the left, and the class file on the right containing the SMAP data.
Verified |