Ping. Bob, I think you had special interest in this one. ;-) On Mon, Jun 15, 2009 at 1:27 PM, Freeland Abbott <[email protected]> wrote:
> Bob notes that dist-dev doesn't need (and thus shouldn't have) its > dependency on tools. I take that as tacit agreement that dist-dev can be > the "minimally build everything for test execution" name. > > > > On Mon, Jun 15, 2009 at 11:53 AM, Freeland Abbott <[email protected]>wrote: > >> Bob, John, can you review? This doesn't address the "buildonly or >> dist-dev as precursor to user/test" question, but I think addresses Thomas' >> and Bob's other issue. >> >> >> >> >> On Mon, Jun 15, 2009 at 11:47 AM, Freeland Abbott <[email protected]>wrote: >> >>> +GWTC >>> >>> With regard to the Mac looking for gwt-dev-linux, since I don't literally >>> see a build-dev target, what's the chain above the line you cited? I >>> thought my fixes to <property.ensure> in e.g. user/build.xml line 47 >>> addressed that, and I see I missed some (in doc, samples, and soyc-vis... >>> only the last of which is likely to be stopping you, though). >>> >>> >>> With regard to using buildonly as precursor to tests, I think you want to >>> the target dist-dev, though I'm open to suggestions for how this "should" >>> work. It used to be that: >>> >>> 1. we had both "build" and "dist," as separate targets (unchanged), >>> 2. tests effectively require a distribution to run in (unchanged), >>> 3. we had "buildonly," but did not have "dist-dev," so the two were >>> blurred explicitly (changed), >>> 4. "build" depended, by way of "-do," on "dist," which I found >>> confusingly backwards (changed), >>> 5. top-level "test" depended on "build", which depended on "dist" as >>> above (changed to depend on "dist-one," but should probably be dist-dev >>> instead now that it exists), >>> 6. "build" was the default target, which as above worked because it >>> ran "dist" as a dependency (changed; "dist" is project default target, >>> and >>> depends on build). >>> >>> Solutions: >>> >>> 1. Do we want buildonly to imply dist-dev? Do we want build to imply >>> dist? My intuition is no, that if separate, build builds and dist >>> packages >>> and dist needs build (but not vice-versa). That is semantic a change >>> from >>> before, though. >>> 2. If not, then we want to retrain ourselves to use dist-dev at least >>> once, to get the distro set, even if you then use buildonly after that to >>> refresh sources? >>> >>> >>> >>> >>> On Mon, Jun 15, 2009 at 11:10 AM, Freeland Abbott <[email protected]>wrote: >>> >>>> Thanks, I'll revisit. >>>> >>>> >>>> >>>> On Mon, Jun 15, 2009 at 10:43 AM, BobV <[email protected]> wrote: >>>> >>>>> >>>>> This no longer correctly works on mac platform. >>>>> >>>>> ant buildonly && cd user && ant test >>>>> /Users/bob/gwt/trunk/common.ant.xml:299: GWT must be built before >>>>> performing any tests. This can be fixed by running ant in the >>>>> /Users/bob/gwt/trunk directory. >>>>> >>>>> >>>>> also, the ant build-dev target fails: >>>>> /Users/bob/gwt/trunk/common.ant.xml:299: Cannot find dependency >>>>> /Users/bob/gwt/trunk/build/lib/gwt-dev-linux.jar >>>>> >>>>> >>>>> -- >>>>> Bob Vawter >>>>> Google Web Toolkit Team >>>>> >>>> >>>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
