Hi,
I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. Can anyone reproduce the error? Cheers, Fabrizio _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hmm, I can reproduce it. I am not sure where it comes from. The cause that come to mind is the recent changes in RB that is moving to Pharo 1.2. We are now loading RB to make sure that it loads in the Core, and this means that when RB changes, it affects the default of Moose.
Cheers, Doru On 12 Nov 2010, at 13:03, Fabrizio Perin wrote: > Hi, > I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. > > Can anyone reproduce the error? > > Cheers, > > Fabrizio > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Thanks Doru. Yep definitely the cause is some modification of RB. What it is not clear is if it is a bug or Moose just load an unstable version (since they are still migrating the system).
Cheers, Fabrizio On 12 Nov 2010, at 16:02, Tudor Girba wrote: > Hmm, I can reproduce it. I am not sure where it comes from. The cause that come to mind is the recent changes in RB that is moving to Pharo 1.2. We are now loading RB to make sure that it loads in the Core, and this means that when RB changes, it affects the default of Moose. > > Cheers, > Doru > > > On 12 Nov 2010, at 13:03, Fabrizio Perin wrote: > >> Hi, >> I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. >> >> Can anyone reproduce the error? >> >> Cheers, >> >> Fabrizio >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "From an abstract enough point of view, any two things are similar." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
"Interactive*Change" were all merged with their superclass "*Change".
Just change the refernces to their superclass and everything should continue to work. Lukas On Friday, November 12, 2010, Fabrizio Perin <[hidden email]> wrote: > Thanks Doru. Yep definitely the cause is some modification of RB. What it is not clear is if it is a bug or Moose just load an unstable version (since they are still migrating the system). > > Cheers, > > Fabrizio > > > On 12 Nov 2010, at 16:02, Tudor Girba wrote: > >> Hmm, I can reproduce it. I am not sure where it comes from. The cause that come to mind is the recent changes in RB that is moving to Pharo 1.2. We are now loading RB to make sure that it loads in the Core, and this means that when RB changes, it affects the default of Moose. >> >> Cheers, >> Doru >> >> >> On 12 Nov 2010, at 13:03, Fabrizio Perin wrote: >> >>> Hi, >>> I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. >>> >>> Can anyone reproduce the error? >>> >>> Cheers, >>> >>> Fabrizio >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "From an abstract enough point of view, any two things are similar." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi,
As I said, the problem appears because right now the default configuration of Moose loads the latest RB code, which no longer works with the OB that is loaded in 1.1. The solution I propose goes like this: we release a 4.2 based on Pharo 1.1, and then we move the development to Pharo 1.2. Any objections? Cheers, Doru On 12 Nov 2010, at 16:38, Lukas Renggli wrote: > "Interactive*Change" were all merged with their superclass "*Change". > Just change the refernces to their superclass and everything should > continue to work. > > Lukas > > On Friday, November 12, 2010, Fabrizio Perin <[hidden email]> wrote: >> Thanks Doru. Yep definitely the cause is some modification of RB. What it is not clear is if it is a bug or Moose just load an unstable version (since they are still migrating the system). >> >> Cheers, >> >> Fabrizio >> >> >> On 12 Nov 2010, at 16:02, Tudor Girba wrote: >> >>> Hmm, I can reproduce it. I am not sure where it comes from. The cause that come to mind is the recent changes in RB that is moving to Pharo 1.2. We are now loading RB to make sure that it loads in the Core, and this means that when RB changes, it affects the default of Moose. >>> >>> Cheers, >>> Doru >>> >>> >>> On 12 Nov 2010, at 13:03, Fabrizio Perin wrote: >>> >>>> Hi, >>>> I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. >>>> >>>> Can anyone reproduce the error? >>>> >>>> Cheers, >>>> >>>> Fabrizio >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> -- >>> www.tudorgirba.com >>> >>> "From an abstract enough point of view, any two things are similar." >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Until someone raises an objection :), I created a baseline42 that does not include RB, and official build based on 1.1 is using this one for now.
Cheers, Doru On 12 Nov 2010, at 18:43, Tudor Girba wrote: > Hi, > > As I said, the problem appears because right now the default configuration of Moose loads the latest RB code, which no longer works with the OB that is loaded in 1.1. > > The solution I propose goes like this: we release a 4.2 based on Pharo 1.1, and then we move the development to Pharo 1.2. > > Any objections? > > Cheers, > Doru > > > On 12 Nov 2010, at 16:38, Lukas Renggli wrote: > >> "Interactive*Change" were all merged with their superclass "*Change". >> Just change the refernces to their superclass and everything should >> continue to work. >> >> Lukas >> >> On Friday, November 12, 2010, Fabrizio Perin <[hidden email]> wrote: >>> Thanks Doru. Yep definitely the cause is some modification of RB. What it is not clear is if it is a bug or Moose just load an unstable version (since they are still migrating the system). >>> >>> Cheers, >>> >>> Fabrizio >>> >>> >>> On 12 Nov 2010, at 16:02, Tudor Girba wrote: >>> >>>> Hmm, I can reproduce it. I am not sure where it comes from. The cause that come to mind is the recent changes in RB that is moving to Pharo 1.2. We are now loading RB to make sure that it loads in the Core, and this means that when RB changes, it affects the default of Moose. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 12 Nov 2010, at 13:03, Fabrizio Perin wrote: >>>> >>>>> Hi, >>>>> I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. >>>>> >>>>> Can anyone reproduce the error? >>>>> >>>>> Cheers, >>>>> >>>>> Fabrizio >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> [hidden email] >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "From an abstract enough point of view, any two things are similar." >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > -- www.tudorgirba.com "Being happy is a matter of choice." _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Tudor Girba
sounds good!
STef On Nov 12, 2010, at 11:01 PM, Tudor Girba wrote: > Until someone raises an objection :), I created a baseline42 that does not include RB, and official build based on 1.1 is using this one for now. > > Cheers, > Doru > > > On 12 Nov 2010, at 18:43, Tudor Girba wrote: > >> Hi, >> >> As I said, the problem appears because right now the default configuration of Moose loads the latest RB code, which no longer works with the OB that is loaded in 1.1. >> >> The solution I propose goes like this: we release a 4.2 based on Pharo 1.1, and then we move the development to Pharo 1.2. >> >> Any objections? >> >> Cheers, >> Doru >> >> >> On 12 Nov 2010, at 16:38, Lukas Renggli wrote: >> >>> "Interactive*Change" were all merged with their superclass "*Change". >>> Just change the refernces to their superclass and everything should >>> continue to work. >>> >>> Lukas >>> >>> On Friday, November 12, 2010, Fabrizio Perin <[hidden email]> wrote: >>>> Thanks Doru. Yep definitely the cause is some modification of RB. What it is not clear is if it is a bug or Moose just load an unstable version (since they are still migrating the system). >>>> >>>> Cheers, >>>> >>>> Fabrizio >>>> >>>> >>>> On 12 Nov 2010, at 16:02, Tudor Girba wrote: >>>> >>>>> Hmm, I can reproduce it. I am not sure where it comes from. The cause that come to mind is the recent changes in RB that is moving to Pharo 1.2. We are now loading RB to make sure that it loads in the Core, and this means that when RB changes, it affects the default of Moose. >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> On 12 Nov 2010, at 13:03, Fabrizio Perin wrote: >>>>> >>>>>> Hi, >>>>>> I started to develop a new tool but i cannot create a new class. When i try save a modified class template i got an error. Apparently the class "Refactoring-Core-Changes>>>InteractiveAddClassChange" has been removed since the build 433 of the Moose. >>>>>> >>>>>> Can anyone reproduce the error? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Fabrizio >>>>>> _______________________________________________ >>>>>> Moose-dev mailing list >>>>>> [hidden email] >>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "From an abstract enough point of view, any two things are similar." >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> [hidden email] >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> [hidden email] >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "Next time you see your life passing by, say 'hi' and get to know her." >> >> >> > > -- > www.tudorgirba.com > > "Being happy is a matter of choice." > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |