Community
Participate
Working Groups
See bug 357257 - for 1.0 we need to update the build process to add SMAP data to the generated runtime class files. Also, we need to start putting the SMAP files into the Java runtime project when the parts are generated. customBuildCallbacks.xml can be used to run a task after the build produces the class files. At this time it's not known if the transformer class from the debug plug-in will be visible. If it isn't, the task can do a CVS checkout, run javac on the transformer class, and invoke it for each SMAP file using a fileset.
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
