ok, ok, thanks ;-)
Loading latest ConfigurationOfEpicea from Epicea's repo and load
bleedingEdge fixes the #name issue in the script.
Tomorrow I can release the new version.
Martin
On Thu, Aug 25, 2016 at 6:10 PM, Tudor Girba wrote:
> Hi,
>
> > On Aug 25, 2016, at 10:03 PM, stepharo wrote:
>
Hi,
> On Aug 25, 2016, at 10:03 PM, stepharo wrote:
>
>
>
> Le 25/8/16 à 14:10, Tudor Girba a écrit :
>> Hi Martin,
>>
>> Thanks a lot for the quick response.
>>
>> As Andrei said, please do not feel sorry. Epicea is an important new core
>> component and just because it is a core one every
Le 25/8/16 à 14:10, Tudor Girba a écrit :
Hi Martin,
Thanks a lot for the quick response.
As Andrei said, please do not feel sorry. Epicea is an important new core
component and just because it is a core one every tiny error will appear as a
large problem. But, we are all humans here, and i
thanks martin!
I really appreciate that you maintain epicea because this is a great tool.
Le 25/8/16 à 13:00, Martin Dias a écrit :
Hi Andrei, there is an open issue that involves #name in category
removal whose fix is ready in bleeding edge and only waits that i
release the new stable ve
Hi Martin,
Thanks a lot for the quick response.
As Andrei said, please do not feel sorry. Epicea is an important new core
component and just because it is a core one every tiny error will appear as a
large problem. But, we are all humans here, and it should be expected that we
make errors :).
Hi Martin,
To reproduce the error execute the code below. The first part does some
cleanups needed to remove the code. The second part attempts to remove two
packages and seems to go into a recursion. If you interrupt the execution
with cmd+. you'll see a lot of Context>>#handleSignal:. If you ri
Hi Andrei, there is an open issue that involves #name in category removal
whose fix is ready in bleeding edge and only waits that i release the new
stable version. But this is about category removal, not class removal. This
night I will take a look on the code of class removal... however, could yo
Hi,
When trying to load a new version of the GTInspector in the latest Pharo
image I get an infinite recursion. It seems that the problem is appears
because a class is removed, which at a certain point calls
#asEpiceaRingDefinition. This does then 'self superclass name', however,
the superclass is
