Re: Doing a release which includes an Eclipse update site
On 30.11.2007, at 05:00, Marshall Schor wrote: Thanks, Erik. It makes sense to me to have the update site under the dist/ directory, since it is a kind of distribution. I see there was an update to the page http://incubator.apache.org/incubation/Incubation_Policy.html about a month ago which added the information that incubator podling releases *must* be on http://www.apache.org/dist/incubator/---podlingname--- Yes, after several long and heated debates I believe this is what was decided, see the thread at [1] for example; the doc you mentioned seems to confirm this but as there is no such location I'm also wondering what the status quo is right now... So I'll make our update site have the form: www.a.o/dist/incubator/uima/ I see in geronimo/eclipse/updates/plugins the jars for the plugins, plus the .asc, md5, and .sha files. How are the .asc, md5, .sha files used? Does the Eclipse update-site signing mechanism interface with these files? No, afaict these are not really used though can't hurt to have them. By the way, I looked at www.a.o/dist/incubator, and it appears that the incubator tree has not yet been set up (I get a URL Not Found). Am I looking in the wrong spot, or have there been no incubator releases since this policy change? It's a pita that we still don't have a www.a.o/dist/incubator - I was under the impression that we're using that already but it seems that the incubator is still using the non-mirrored and non-archived location at people.apache.org/dist/incubator/... Cheers, Erik [1] http://marc.info/?t=11720166144r=1w=2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Doing a release which includes an Eclipse update site
In our next release of Apache UIMA from the incubator, we would like to include an additional packaging of some of our Eclipse tooling as an Eclipse update site. This is a location, reachable via http, which Eclipse can use to download Eclipse plugins. Doing this solves a long-standing complaint because this method does version / dependency checking for other needed Eclipse plugins. Several projects at Apache make use of Eclipse update sites; all of them (I think) host them off of their project web sites. This is what we would like to do. Is this OK to do (once the release is voted on, and passes, of course) ? -Marshall Schor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Doing a release which includes an Eclipse update site
On 29.11.2007, at 22:41, Marshall Schor wrote: In our next release of Apache UIMA from the incubator, we would like to include an additional packaging of some of our Eclipse tooling as an Eclipse update site. This is a location, reachable via http, which Eclipse can use to download Eclipse plugins. Doing this solves a long-standing complaint because this method does version / dependency checking for other needed Eclipse plugins. Several projects at Apache make use of Eclipse update sites; all of them (I think) host them off of their project web sites. This is what we would like to do. Off of their project web sites? Hmm, I'd suggest to do it like Geronimo and use your /dist/ area: http://www.apache.org/dist/geronimo/eclipse/updates/ and also tie it into the current mirroring system; for an example see site.xml at that location, esspecially the site mirrorsURL=... in there which refers to [1] and which takes care of delivering the locations of the currently available mirrors... Cheers, Erik [1] http://geronimo.apache.org/devtools/geronimo-eclipse-update--xml.cgi for the source see https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/devtools/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Doing a release which includes an Eclipse update site
Thanks, Erik. It makes sense to me to have the update site under the dist/ directory, since it is a kind of distribution. I see there was an update to the page http://incubator.apache.org/incubation/Incubation_Policy.html about a month ago which added the information that incubator podling releases *must* be on http://www.apache.org/dist/incubator/---podlingname--- So I'll make our update site have the form: www.a.o/dist/incubator/uima/ I see in geronimo/eclipse/updates/plugins the jars for the plugins, plus the .asc, md5, and .sha files. How are the .asc, md5, .sha files used? Does the Eclipse update-site signing mechanism interface with these files? By the way, I looked at www.a.o/dist/incubator, and it appears that the incubator tree has not yet been set up (I get a URL Not Found). Am I looking in the wrong spot, or have there been no incubator releases since this policy change? -Marshall Erik Abele wrote: On 29.11.2007, at 22:41, Marshall Schor wrote: In our next release of Apache UIMA from the incubator, we would like to include an additional packaging of some of our Eclipse tooling as an Eclipse update site. This is a location, reachable via http, which Eclipse can use to download Eclipse plugins. Doing this solves a long-standing complaint because this method does version / dependency checking for other needed Eclipse plugins. Several projects at Apache make use of Eclipse update sites; all of them (I think) host them off of their project web sites. This is what we would like to do. Off of their project web sites? Hmm, I'd suggest to do it like Geronimo and use your /dist/ area: http://www.apache.org/dist/geronimo/eclipse/updates/ and also tie it into the current mirroring system; for an example see site.xml at that location, esspecially the site mirrorsURL=... in there which refers to [1] and which takes care of delivering the locations of the currently available mirrors... Cheers, Erik [1] http://geronimo.apache.org/devtools/geronimo-eclipse-update--xml.cgi for the source see https://svn.apache.org/repos/asf/geronimo/site/trunk/docs/devtools/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
