Re: superunstable

From: David Avendasora (webobject..vendasora.com)
Date: Mon Feb 11 2008 - 12:38:32 EST

  • Next message: Apoorva Muralidhara: "Re: Problem showing project images in app ported from XCode"

    I'd like to at least give it a shot on a separate Eclipse install,
    and I wouldn't expect immediate fixes. Because I'm deploying to a
    servlet and doing Java Client, I _know_ I have some "crazy" Ant stuff
    going on and I'd like the chance to make some pre-rollout updates
    available on the WIki so others making the transition would have
    someplace to start.

    Either that, or I'm just masochistic.

    Maybe instead of "superunstable" it could be called "areyouinsane".

    Dave

    On Feb 11, 2008, at 12:30 PM, Sebastien wrote:

    > Mike,
    >
    > What about a temporary branch so a few of us can test out the
    > complete changes you were initially thinking of committing ? Since
    > there seems to be a few of us willing to give a shot at it, it
    > might be a good test to see if it's ready for a wider audience. I'm
    > actually holding off any change as well for my team until I get a
    > change to try your new stuff, as it's been nightmarish as it stands
    > today.
    >
    > Just my thought.
    >
    > Sebastien
    >
    > On Feb 11, 2008, at 8:43 AM, Chuck Hill wrote:
    >
    >>
    >> On Feb 11, 2008, at 6:28 AM, Mike Schrag wrote:
    >>
    >>>>>> Any news on that topic? Can't wait...
    >>>>>>
    >>>>>> I'm still stuck with 4606, as I could not get my projects
    >>>>>> working reliably with the changes to classpath handling in
    >>>>>> 4607 (there is already a unique instance of bundle "bla"...).
    >>>>>> After hours and hours of fiddling I finally gave up. Now the
    >>>>>> upcoming "superunstable" change could bring back the fun... :)
    >>>>>>
    >>>>>> Timo
    >>>>> I'm sort of in a holding pattern and having second thoughts ...
    >>>>> If I commit, I also commit myself to a lot of work, because the
    >>>>> ant build portion is most likely going to break in a lot of
    >>>>> funky cases (who knows what people do in those ant files). I
    >>>>> don't know if I want to deal with it right now, so I'm just
    >>>>> putting it off. I'm thinking about just fixing a couple of the
    >>>>> notable regressions in the current one -- the double selection
    >>>>> of local + system frameworks, the P/Whatever error during
    >>>>> conversion, and the unique framework bug -- which incidentally
    >>>>> only doesn't happen to me because I have a custom NSBundle that
    >>>>> works around that problem.
    >>>>
    >>>> If you can fix those inside the current branch, I think it will
    >>>> solve most problems that people are currently having.
    >>> This was my thought too ... I've also been considering just
    >>> changing the Eclipse portion, but leaving the ant.* stuff. So
    >>> you get the dynamic classpath management stuff but without
    >>> changing the ant side too drastically.
    >>
    >> Most of them, but the ant side is still, well, like it is. But it
    >> would be good to at least get rid of some of that badness.
    >>
    >> Chuck
    >>
    >> --
    >>
    >> Practical WebObjects - for developers who want to increase their
    >> overall knowledge of WebObjects or who are trying to solve
    >> specific problems.
    >> http://www.global-village.net/products/practical_webobjects
    >>
    >>
    >>
    >>
    >>
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Mon Feb 11 2008 - 12:40:14 EST