>
>
> What would be involved in automating the plugin build process?  Are we
> talking Maven + Ant + shell scripting?
>
>
Although they were usually minor, there are definitely changes in each
release.

I am trying to create scripts here and there but in reality, it is very hard
automatic  upstream API changes.


> And actually, this was more or less the answer I wanted to hear.  The
> post was a "why" much more than a "would you please fix".
>
> FWIW, I finally found
>
> ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/
>
> Here you can get every Firefox release, not just the "supported"
> ones.  One of the big frustrations of all this was the inability to
> actually get my hands on the latest supported version, once the next
> unsupported version came out (esp. since it seemed that every time a
> new GWT Plugin came out, there'd be a new, unsupported version of
> Firefox out before I could get my hands on the now supported
> version).  Having that link takes this all from a major irritation to
> a minor one.
>
> Greg
>
> On Oct 3, 1:51 pm, Chris Conroy <[email protected]> wrote:
> > I've mentioned this in other threads, but I'll repeat here: Under the new
> > rapid-release model, Mozilla is intentionally breaking binary
> compatibility
> > with xpcom components on every release. We are forced to rebuild for
> every
> > platform with every release.
> >
> > Our existing processes for maintaining the plugin come from a time long
> > before this model. Due to the number of platforms that we support,
> manually
> > building a new release of the plugin takes a decent amount of time.
> Mozilla
> > has said that the binary API can change up until the official release, so
> > that rules out attempting to start on this work early. Moreover, future
> > updates will almost certainly have real breaking changes that could
> require
> > significant time to address.
> >
> > In the meantime, I would suggest running against whatever version of
> Firefox
> > is supported. If some version specific issue comes up that you must debug
> > before we can get a release out, then you may just have to build the
> plugin
> > yourself. But, these 'major' releases are really quite minor. In
> > all likelihood, any issue you want to debug in DevMode will surface in
> the
> > same way in FF6 as in FF7.
> >
> > I know this isn't the answer you (or many people) want to hear, but
> that's
> > the reality today.
> >
> > P.S.
> > I would advise people on this list to be cautious about downloading
> plugin
> > binaries from other people. It's much safer to build your own from source
> or
> > wait for an official release.
> >
> > On Mon, Oct 3, 2011 at 10:19 AM, Gregory Dougherty <[email protected]
> >wrote:
> >
> >
> >
> >
> >
> >
> >
> > > For those of us who debug our GWT apps in Firefox, and would kind of
> > > like to keep up to date on Firefox releases, could someone from Google
> > > give a quick rundown on why it is that each of the last three (four ?)
> > > Firefox releases has broken the Dev Plugin, apparently each in new
> > > ways?  Are the people working of Firefox just doing stupid things?
> > > Does the GWT Developer Plugin just assume that it must be incompatible
> > > with any X+1.0 release?
> >
> > > Why is it that the Developer Plugin for Firefox only seems to get
> > > "cleared" for the current version of Firefox less than a week before
> > > the next ("hyper critical, be sure to replace your previous version")
> > > version comes out?
> >
> > > TIA,
> >
> > > Greg
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google Web Toolkit" group.
> > > To post to this group, send email to
> [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected].
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-web-toolkit?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to