Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EDT:How to update system parts"
| Line 10: | Line 10: | ||
#If you have ANY problems in your problem view, attempt to do a second clean build on both projects to see if that cleans things up. If this still doesnt work, you will need to open a bugzilla bug. | #If you have ANY problems in your problem view, attempt to do a second clean build on both projects to see if that cleans things up. If this still doesnt work, you will need to open a bugzilla bug. | ||
#If you have gotten this far, now you will want to package up the archive files. There are 2 ant scripts in the external tools dropdown. If you have made changes to the mof model (the egl source in edt.mof.egl), run the one named Build_MofEGL_MOFAR. Otherwise, your changes must be in edt.compiler. so run Build_Compiler_EGLAR. | #If you have gotten this far, now you will want to package up the archive files. There are 2 ant scripts in the external tools dropdown. If you have made changes to the mof model (the egl source in edt.mof.egl), run the one named Build_MofEGL_MOFAR. Otherwise, your changes must be in edt.compiler. so run Build_Compiler_EGLAR. | ||
| − | #Now, you simply commit your changes to the .egl and EGLAR and/or MOFAR to | + | #Now, you simply commit your changes to the .egl and EGLAR and/or MOFAR to Git. |
#You will need to release the changed files so they are included in the build. You can either load the files from your development workspace and release from there, or if you are using an EDT build, you will need to follow the instructions in [[EDT:How to commit code to EDT|EDT:How_to_commit_code_to_EDT]] | #You will need to release the changed files so they are included in the build. You can either load the files from your development workspace and release from there, or if you are using an EDT build, you will need to follow the instructions in [[EDT:How to commit code to EDT|EDT:How_to_commit_code_to_EDT]] | ||
Revision as of 10:41, 1 November 2012
If you need to edit our system types (either the EGL or the Mof), to add new types or change existing ones, follow these steps:
- Bring up a runtime workspace (either from a Development workspace, or use an EDT build). I recommend you use a clean workspace.
- Load the following projects from dev.eclipse.org:
- org.eclipse.edt.compiler
- org.eclipse.edt.mof.egl
- The projects are EGL projects, so you will be able to make your changes in the EGL editor.
- Now, to compile your changes, you should do a clean build on both projects. This is required because the definitions of some of the types in the mof model have a different name than what is saved as an IR. By doing a clean build, the validator can use the EGL source to get the bindings, instead of reading the IRs off of the disk.
- If all has gone well, you should have NO validation errors in your workspace.
- If you have ANY problems in your problem view, attempt to do a second clean build on both projects to see if that cleans things up. If this still doesnt work, you will need to open a bugzilla bug.
- If you have gotten this far, now you will want to package up the archive files. There are 2 ant scripts in the external tools dropdown. If you have made changes to the mof model (the egl source in edt.mof.egl), run the one named Build_MofEGL_MOFAR. Otherwise, your changes must be in edt.compiler. so run Build_Compiler_EGLAR.
- Now, you simply commit your changes to the .egl and EGLAR and/or MOFAR to Git.
- You will need to release the changed files so they are included in the build. You can either load the files from your development workspace and release from there, or if you are using an EDT build, you will need to follow the instructions in EDT:How_to_commit_code_to_EDT