Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Re: [cross-project-issues-dev] GO for Upload/rename - EMF is ready

Jars (and thus feature.xml files) are unchanged. site.xml has a new
entry on OUR update site; site-interim.xml still contains info about
the RC6 features (which are now renamed and listed in site.xml as
well).  Does the Europa-o-matic look at the feature names as listed in
the site*.xml file? or just the values in the europa-ste/site.xml? If
the latter, then I guess we're ok here.

At some point I'll be cleaning out the old pre-release entries in
site-interim.xml, which is why I was wondering if a respin would be
useful so that the Europa-o-matic could now look at the site.xml file
instead of the site-interim.xml file.

Anyway, I guess we're fine. Sorry for the scare. ;-)


On 6/28/07, Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> wrote:

 If the Europa release update site is working for you right now, then no
re-spin is necessary. The features-*.xml file only tells Europa-matic where
to find the files but that file location information is not propagated to
the update site itself. On the update site, the separate feature.xml files
have your update site information in them. If you've changed _that_ then we
would need a respin. I am assuming that you have not changed that.

 - Bjorn

 Nick Boldt wrote:
I don't know if this matters, but the features-emf-emf.xml file has
 been updated too, because now that we have a release, it's on site.xml
 instead of site-interim.xml, with "2.3.0" instead of "2.3.0RC6" in the
 feature names. I presume this will require a respin?

 Nick Boldt :: Release Engineer, IBM Toronto Lab
 Eclipse Modeling ::
 cross-project-issues-dev mailing list

_______________________________________________ mailing list

Back to the top