moose build broke due to ConfigurationOfNautilus

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

moose build broke due to ConfigurationOfNautilus

Tudor Girba-2
Hi,

The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus.

In general, it would be great to remove as little methods as possible from Configuration classes.

Cheers,
Doru


--
www.tudorgirba.com

"Speaking louder won't make the point worthier."


Reply | Threaded
Open this post in threaded view
|

Re: moose build broke due to ConfigurationOfNautilus

fstephany
It confuses me that some projects have their own set of class methods to
load groups.

Would not it be better to just call
ConfigurationOfNautilus project stable load: 'Refactorings' ?

What is the recommended practice?

On 18/04/12 23:17, Tudor Girba wrote:

> Hi,
>
> The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus.
>
> In general, it would be great to remove as little methods as possible from Configuration classes.
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "Speaking louder won't make the point worthier."
>
>

--
http://tulipemoutarde.be
CA: +1 778 558 3225
BE: +32 65 709 131

Reply | Threaded
Open this post in threaded view
|

Re: moose build broke due to ConfigurationOfNautilus

philippeback
+1000

2012/4/19 Francois Stephany <[hidden email]>
It confuses me that some projects have their own set of class methods to load groups.

Would not it be better to just call
ConfigurationOfNautilus project stable load: 'Refactorings' ?

What is the recommended practice?

On 18/04/12 23:17, Tudor Girba wrote:
Hi,

The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus.

In general, it would be great to remove as little methods as possible from Configuration classes.

Cheers,
Doru


--
www.tudorgirba.com

"Speaking louder won't make the point worthier."



--
http://tulipemoutarde.be
CA: <a href="tel:%2B1%20778%20558%203225" value="+17785583225" target="_blank">+1 778 558 3225
BE: <a href="tel:%2B32%2065%20709%20131" value="+3265709131" target="_blank">+32 65 709 131




--
Philippe Back
"Helping you hit the top 3 outcomes you really want to achieve"

Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: [hidden email] | Web: http://philippeback.eu | Blog:

High Octane SPRL
rue cour Boisacq 101
1301 Bierges

Reply | Threaded
Open this post in threaded view
|

Re: moose build broke due to ConfigurationOfNautilus

Benjamin Van Ryseghem (Pharo)
In reply to this post by Tudor Girba-2
I am sorry :(

But we were preparing Nautilus for Pharo 2.0, and we wanted to reduce the amount of groups to not disturb to much users.

So now there are 'core' and 'release' groups...


Sorry again, and thank you for using Nautilus :)

Ben

On Apr 19, 2012, at 8:17 AM, Tudor Girba wrote:

> Hi,
>
> The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus.
>
> In general, it would be great to remove as little methods as possible from Configuration classes.
>
> Cheers,
> Doru
>
>
> --
> www.tudorgirba.com
>
> "Speaking louder won't make the point worthier."
>
>


Reply | Threaded
Open this post in threaded view
|

Re: moose build broke due to ConfigurationOfNautilus

Tudor Girba-2
Hi,

It's not a problem.

I fixed the problem easily, but I was just raising the issue so that
we can prevent it in the future, perhaps through communication.

Cheers,
Doru


On Thu, Apr 19, 2012 at 1:05 PM, Benjamin
<[hidden email]> wrote:

> I am sorry :(
>
> But we were preparing Nautilus for Pharo 2.0, and we wanted to reduce the amount of groups to not disturb to much users.
>
> So now there are 'core' and 'release' groups...
>
>
> Sorry again, and thank you for using Nautilus :)
>
> Ben
>
> On Apr 19, 2012, at 8:17 AM, Tudor Girba wrote:
>
>> Hi,
>>
>> The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus.
>>
>> In general, it would be great to remove as little methods as possible from Configuration classes.
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Speaking louder won't make the point worthier."
>>
>>
>
>



--
www.tudorgirba.com

"Every thing has its own flow"

Reply | Threaded
Open this post in threaded view
|

Re: moose build broke due to ConfigurationOfNautilus

Benjamin Van Ryseghem (Pharo)
You are right,

I had totally forgotten than Moose was depending on Nautilus :s

But now, it should not change for a while (the configuration API ^^)

Sorry again,

Ben

On Apr 19, 2012, at 1:15 PM, Tudor Girba wrote:

> Hi,
>
> It's not a problem.
>
> I fixed the problem easily, but I was just raising the issue so that
> we can prevent it in the future, perhaps through communication.
>
> Cheers,
> Doru
>
>
> On Thu, Apr 19, 2012 at 1:05 PM, Benjamin
> <[hidden email]> wrote:
>> I am sorry :(
>>
>> But we were preparing Nautilus for Pharo 2.0, and we wanted to reduce the amount of groups to not disturb to much users.
>>
>> So now there are 'core' and 'release' groups...
>>
>>
>> Sorry again, and thank you for using Nautilus :)
>>
>> Ben
>>
>> On Apr 19, 2012, at 8:17 AM, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> The Moose build just broke due to the loadRefactorings method being removed from ConfigurationOfNautilus.
>>>
>>> In general, it would be great to remove as little methods as possible from Configuration classes.
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Speaking louder won't make the point worthier."
>>>
>>>
>>
>>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>