Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Modeling Project Releng/Releasing/Update Site Generation"
m |
|||
| Line 51: | Line 51: | ||
If you encounter any [http://wiki.eclipse.org/index.php?title=EMFT_Procedures#Promotion_Problems_.28CVS_Errors.2C_SCP_Errors.2C_Artifacts_Not_Created....29 problems setting up or running the UM generation code], there's a sample of the build script output with an explanation of what went wrong on the [[EMFT_Procedures|EMFT Procedures]] document. | If you encounter any [http://wiki.eclipse.org/index.php?title=EMFT_Procedures#Promotion_Problems_.28CVS_Errors.2C_SCP_Errors.2C_Artifacts_Not_Created....29 problems setting up or running the UM generation code], there's a sample of the build script output with an explanation of what went wrong on the [[EMFT_Procedures|EMFT Procedures]] document. | ||
| + | |||
| + | |||
| + | [[Category:Modeling]] | ||
| + | [[Category:Releng]] | ||
Revision as of 22:28, 10 September 2006
This article is a stub. You can help Eclipsepedia by expanding it.
This document describes - albeit briefly - how to generate incremental Update Manager site content from nothing more than a ready-to-publish SDK zipfile.
This document will evolve over time. For now, have a look at the following links:
Setup
- README
- scripts folder, containing:
- buildUpdate.sh, where the magic begins
- properties file, properties used by the above script
- build.options.txt, mappings used by the above script
- releng/common/updates folder, code used to generate the jars
- /cvsroot/org.eclipse/www/emft/updates folder, where the site*.xml files are stored in order to add content incrementally
Output
After running the scripts, you end up with XML that looks like this:
http://www.eclipse.org/emft/updates/
And jars that look like this:
nickb@download1.eclipse.org:/home/data/httpd/download.eclipse.org/technology/emft/updates $ find . -name "*200608241538*" ./md5s/transaction_M200608241538.md5 ./features/org.eclipse.emf.transaction.doc_1.0.0.v200608241538.jar ./features/org.eclipse.emf.workspace.source_1.0.0.v200608241538.jar ./features/org.eclipse.emf.workspace.examples.source_1.0.0.v200608241538.jar ./features/org.eclipse.emf.transaction.examples_1.0.0.v200608241538.jar ./features/org.eclipse.emf.workspace.doc_1.0.0.v200608241538.jar ./features/org.eclipse.emf.workspace_1.0.0.v200608241538.jar ./features/org.eclipse.emf.transaction_1.0.0.v200608241538.jar ./features/org.eclipse.emf.transaction.examples.source_1.0.0.v200608241538.jar ./features/org.eclipse.emf.workspace.examples_1.0.0.v200608241538.jar ./features/org.eclipse.emf.transaction.sdk_1.0.0.v200608241538.jar ./features/org.eclipse.emf.transaction.source_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.transaction.doc_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace.source_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace.examples.source_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.transaction.examples_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace.doc_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace.examples.library.editor_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace.ui_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.transaction_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.transaction.ui_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.transaction.examples.source_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.workspace.examples_1.0.0.v200608241538.jar ./plugins/org.eclipse.emf.transaction.source_1.0.0.v200608241538.jar
If you encounter any problems setting up or running the UM generation code, there's a sample of the build script output with an explanation of what went wrong on the EMFT Procedures document.