Re: [eclipse.org-planning-council] Europa re-spins and Europa Fal l main

["Nick Boldt" <nickboldt@xxxxxxxxx>]

Doug:

It's not every jar, just a few key feature jars -- sdk, runtime,
emf.ecore, etc. Also, but filtering through download.php?r=1, a
random/best site is picked automagically, so I'm *hoping* performance
won't suffer.

On 7/25/07, Doug Schaefer <DSchaefer@xxxxxxx> wrote:
> Yes, I'm sure Denis has had similar conversations with all of us. I'm not
> sure what happened where this used to work but does no longer. But it looks
> like we've lost our download stats unless we want to invest in the tools to
> do as you suggest. I worry about update performance though if every jar
> needs to go to download.php.
>
> Doug Schaefer, QNX Software Systems
> Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
>
>
> > -----Original Message-----
> > From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
> > [mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of
> > Nick Boldt
> > Sent: Wednesday, July 25, 2007 12:04 PM
> > To: eclipse.org-planning-council
> > Cc: bjorn@xxxxxxxxxxx
> > Subject: Re: [eclipse.org-planning-council] Europa re-spins and Europa
> > Fall maintenance and Europa-matic currently fails
> >
> > I can explain the EMF and MDT failures.
> >
> > We want to track who's downloading [1] our bits -- zips and update
> > jars. In order to be able to do so for the jars, I spoke with Denis
> > and his suggestion [2] was to embed the download.php URL in the update
> > site xml. This I did, then added it to our builder so it does it for
> > all our projects.
> >
> > [1] http://www.eclipse.org/modeling/emf/downloads/stats.php
> > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=195022
> >
> > The result is that our site.xml looks like this:
> >
> >       <feature id="org.eclipse.emf.sdk" version="2.3.1.v200707171853"
> > url="http://www.eclipse.org/downloads/download.php?r=1&amp;file=/modeling/
> > EMF/updates/features/org.eclipse.emf.sdk_2.3.1.v200707171853.jar"
> > patch="false">
> >               <category name="EMF SDK 2.3.1 M200707171853"/>
> >       </feature>
> >
> > instead of the simpler and untrackable:
> >
> >       <feature id="org.eclipse.emf.sdk" version="2.3.1.v200707171853"
> > url="features/org.eclipse.emf.sdk_2.3.1.v200707171853.jar"
> > patch="false">
> >               <category name="EMF SDK 2.3.1 M200707171853"/>
> >       </feature>
> >
> > So, I throw myself at the mercy of the O'Matic and beg for both
> > forgiveness and the added support for stripping everything in the
> > <feature url=""/> attribute before 'features/' when parsing the XML to
> > find files, but keeping it when generating the output site.xml for
> > download stat tracking.
> >
> > Is this doable?
> >
> > Nick
> >
> >
> > On 7/25/07, Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> wrote:
> > >
> > >  Planning Council Members involved in Europa,
> > >  The Europa-matic build is currently failing on Platform, EMF and MDT.
> > >  http://dash.eclipse.org/~bfreeman/europa/
> > >
> > >  Please update your features-*.xml files so that the Europa-matic
> > succeeds
> > > green.
> > >  I ask this for two reasons:
> > >
> > >
> > > There are some projects (you've seen the email trail here) who are
> > asking
> > > for a re-spin to fix certain critical bugs. While the issues of whether
> > to
> > > re-release is still under discussion (and will probably only be solved
> > on a
> > > phone call), we'd still like to have the release train be buildable so
> > that
> > > we can proceed forward to a re-release if we, collectively, decide to do
> > so.
> > > The Europa Fall Maintenance release (September 24-28; a short 62 days
> > from
> > > now) will be using the same Europa-matic. Thus it behooves us to make
> > sure
> > > that Europa-matic can build the train so that we can do that maintenance
> > > release. Thanks for your attention to these build failures,
> > >  Bjorn
> > >
> > >
> > > _______________________________________________
> > > eclipse.org-planning-council mailing list
> > > eclipse.org-planning-council@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
> > >
> > >
> > _______________________________________________
> > eclipse.org-planning-council mailing list
> > eclipse.org-planning-council@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council