The last version loads in 1.4 if I remove the inst var duplication
Ben On Jul 31, 2012, at 9:47 AM, Stéphane Ducasse wrote: > > On Jul 31, 2012, at 4:14 AM, Benjamin wrote: > >> I will but when I publish a Spec version from 2.0, I can't know this kind of >> bug > > if you give me access to the spec repo I can do it. > The point is that for 1.4 do you want to publish the newest version? I would > not I would simply take the old version > and make sure that it loads in 1.4 > > Stef >> >> Ben >> >> On Jul 30, 2012, at 11:15 PM, Stéphane Ducasse wrote: >> >>> ben >>> may be you should just fix the problem as I did and publish a stable >>> version that load in 1.4 >>> This way people can load spec (the stable version for 1.4) in 1.4. >>> we can do it together. Now going to bed >>> >>> Stef >>> >>> On Jul 30, 2012, at 10:55 PM, Benjamin wrote: >>> >>>> NautilusRefactoring depends on Spec for the UI, that's all. >>>> >>>> But the problem is that in 2.0 a subclass can have an inst var named like >>>> ones of its superclasses ... >>>> >>>> Ben >>>> >>>> >>>> On Jul 30, 2012, at 10:22 PM, Stéphane Ducasse wrote: >>>> >>>>> >>>>> On Jul 30, 2012, at 9:54 PM, Benjamin wrote: >>>>> >>>>>> >>>>>> On Jul 30, 2012, at 7:22 PM, Stéphane Ducasse wrote: >>>>>> >>>>>>> Yes I got bitten by that today this is a problem you should remove the >>>>>>> instance variable from the superclass then load and remove it from >>>>>>> buttonModel >>>>>>> and add it to its superclass. >>>>>>> Now I suggest not to use nautilus for 1.4. >>>>>> >>>>>> Why ? >>>>> >>>>> Indeed nautilus is not base on spec. >>>>> Still let us focus on 2.0 >>>>> >>>>> Stef >>>>> >>>>>> >>>>>> Ben >>>>>> >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jul 30, 2012, at 7:02 PM, Patrik Sundberg wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Loading nautilus #stable in 1.4 I get: >>>>>>>> DuplicatedVariableError: helpHolder is already defined in >>>>>>>> AbstractBasicWidget >>>>>>>> >>>>>>>> Looks to come when loading the dependency >>>>>>>> Spec-Widgets-BenjaminVanRyseghem.48. >>>>>>>> >>>>>>>> Any ideas? >>>>>>>> >>>>>>>> I can provide more of the stack trace if it's useful (I'd assume so), >>>>>>>> but would like a pointer what the best way to get that info in an >>>>>>>> emailable format (not obvious to me how I can just copy-paste it). >>>>>>>> >>>>>>>> This is the summer release. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Patrik >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
