will take a look :-) -Marshall
On 11/25/2019 11:06 AM, Peter Klügl wrote: > Hi, > > > I've read the page on our website and even remembered what we did years > ago when the composite site was refactored. > > I am of course aware of our time difference and I planned to wait for > your response, but then I just gave it a try and it worked better than > expected. Do you think that could be a problem for the RC? > > > Best, > > > Peter > > > Am 25.11.2019 um 16:55 schrieb Marshall Schor: >> Hi, >> >> I found a bunch of stuff from my last work on composite update sites (and >> plain >> update sites), and found I had not check these into svn. I've just fixed >> that... >> >> These are in the "build" set of projects: uima-eclipse-composite-update-site >> (was updated previously to set up the version 3 composite update site), and >> uima-eclipse-update-site-removing - a small utility for running eclipse >> utilities to remove older update sites. There's also a >> uima-eclipse-update-site-slicing - used when you want to move some older >> update >> sites to an "archive" spot. >> >> Here's a quick summary: Because uima v3 things are not compatible with v2 >> things >> (due to JCas being different), we have 2 eclipse update composite sites: The >> v2 >> one is "eclipse-update-site", The v3 one is "eclipse-update-site-v3". >> >> (We also have another update site, called "archive-eclipse-update-site" - >> which >> you should use to move much older and no longer actively needed versions (but >> which you still want users to be able to find if needed). >> >> Our website downloads page has a section for Eclipse Update Sites which also >> has >> these links, and reference to the archive: >> >> http://uima.apache.org/downloads.cgi#Eclipse%20Update%20Site >> >> The page >> https://uima.apache.org/eclipse-update-site.html#Composite%20Update%20Sites >> on >> our website (linked from the left-hand nav bar) has instructions (which >> ought to >> be reviewed for correctness / sanity / :-) ) on how to update the composite >> site(s) when needed. >> >> see >> https://uima.apache.org/eclipse-update-site.html#Composite%20Update%20Sites >> >> Finally, remember you have the option of "signing" the Jars used in the >> update >> site, so that when users install your plugins, they no longer get those >> messages >> about "you are about to install unsigned .... ". Instructions for how to do >> this are here: >> https://uima.apache.org/dev-eclipse-plugin-signing.html (probably need to >> add >> more links to this. There's one in the >> https://uima.apache.org/checklist-release.html doc... >> >> -Marshall >> >> On 11/25/2019 4:06 AM, Peter Klügl wrote: >>> Hi, >>> >>> >>> I wonder how the Ruta v3 update is released and how I should prepare the RC. >>> >>> >>> There is no subsite yet, so I assume the composite update site needs to >>> be updated and thus also needs to be reviewed/released. >>> >>> Should we do that in one process or in two? Should the RC for the update >>> site contain only the subsite as we normally do it or should I prepare a >>> complete update site including uimaj and an updated composite? >>> >>> >>> I think I go with the second option... opinions? >>> >>> >>> Best, >>> >>> >>> Peter >>> >>>
