Difference between revisions of "Galileo/Final Daze/Modeling Project"
|Line 1:||Line 1:|
== Projects ==
== Projects ==
Below is the list of projects in Galileo.
Below is the list of projects in Galileo . , component.
Note that it's perfectly acceptable for multiple '''projects''' to publish concurrently, since they each have separate update sites. The only limitation is on components who share a common site.
Note that it's perfectly acceptable for multiple '''projects''' to publish concurrently, since they each have separate update sites. The only limitation is on componentswho share a common site.
|Line 16:||Line 18:|
|Line 35:||Line 33:|
== FAQ ==
== FAQ ==
Revision as of 12:41, 18 June 2009
Below is the list of projects in Galileo which have components. (GEF, GMF, and TMF-Xtext are also in Galileo but are single-component-projects.)
Please ensure that for projects w/ multiple component, only one component promotes their bits at a time. I suggest that each component lead should sign up below with the time they plan to do their promote below, so that no overlapping occurs.
Note that it's perfectly acceptable for multiple projects to publish concurrently, since they each have separate update sites. The only limitation is on components who share a common site.
EMF (Core) Query, Transaction, Validation, Teneo Net4j, CDO
EMF Compare Ecore Tools Mint MWE
OCL UML2 UML2 Tools XSD
JET Xpand Acceleo
What exactly to do for modelling projects and when?
Last year we met on IRC in #eclipse-modeling to make sure that projects were published in the correct order:
The only real limitation w/ the current system is that people should NOT PROMOTE their final, renamed or rebuilt builds AT THE SAME TIME within the same project, as this will corrupt the p2 metadata generation process, and you'll end up with an unusable update site.
Seems like we should make our release build on Monday but should not promote them, right?
You can promote them as soon as they're ready; there's a file in CVS which controls the visibility of R builds, for example:
If there's a build ID listed in that file, it will NOT be shown on the downloads page, but will be available for the mirrors to pick it up and replicate it. If you remove the entry in the file, it will mark the build visible on www.eclipse.org.
But update site are created only if one promote them, is there a workaround?
What about .build files?
Create them by hand, or create them as part of the publishing/promoting script. Your choice. You can also generate them using
/home/www-data/build/modeling/scripts/promoteToEclipse.sh and the
-coordsiteonly galileo flag. Run the script without options to get detailed usage instructions re: the other required flags.