Yeah. Our 2.0 site.xml must be merged into the existing one, so both the old and new versions may coexist on the same site.
Ted Kirby On 9/29/07, Kan Ogawa <[EMAIL PROTECTED]> wrote: > Tim, > > There is not v2.0.0 feature in site.xml. When this is updated? > http://www.apache.org/dist/geronimo/eclipse/updates/site.xml > > -- > Kan Ogawa > [EMAIL PROTECTED] > > Tim McConnell (JIRA) wrote: > > [ > > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > ] > > > > Tim McConnell closed GERONIMODEVTOOLS-226. > > ------------------------------------------ > > > > Resolution: Fixed > > Fix Version/s: 2.0.0 > > > > Hi Ted, thanks for pointing out this problem. I misunderstand the process > > necessary to update the "update site". I understand it now, and have fixed > > the problem. I've also updated our "Release Eclipse Plugin Process" wiki > > (http://cwiki.apache.org/GMOxPMGT/release-eclipse-plugin-process.html) to > > ensure it doesn't happen again. > > > > > >> Production eclipse udate site does not have 2.0.0 on it! > >> -------------------------------------------------------- > >> > >> Key: GERONIMODEVTOOLS-226 > >> URL: > >> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-226 > >> Project: Geronimo-Devtools > >> Issue Type: Bug > >> Components: eclipse-plugin > >> Affects Versions: 2.0.0 > >> Reporter: Ted Kirby > >> Assignee: Tim McConnell > >> Priority: Blocker > >> Fix For: 2.0.0 > >> > >> > >> The staging site > >> http://people.apache.org/~mcconne/releases/RC3/staging_site > >> looks good, > >> but the production site > >> http://www.apache.org/dist/geronimo/eclipse/updates/plugins/ > >> does not have the new stuff on it. > >> Do we want to keep the old stuff there also, or just nuke it and put the > >> v20 stuff there? > >> Or, create a new udpate site for v2? > > >
