Hi Stef,
I found where is the last issue. I can correct the symptoms, but I don't
know why it happens. Not yet.
I'm not sure it covers the previous ones, but it may also be the same.
Thierry
Le 09/04/2015 22:42, stepharo a écrit :
Hi johan
I usually attract bugs but not these ones.
- I got debugger freezing
- broken refactoring
but not that ones. I would love to have a way to reproduce it.
Stef
Le 8/4/15 19:41, Johan Brichau a écrit :
Hi all,
Over the last week, I started working with Pharo4, mostly to make
Seaside work cleanly.
On several occasions, I had severe issues with the package management:
- methods that were changed in a class were not recorded as ‘changed’
in monticello and were absent from the published package
- versions of methods disappeared (i.e. no longer accessible in the
version history of a method)
- looking at the ‘changed’ in Monticello showed all code of the
package as changed (though only a single method has changed).
This makes working with Pharo4 extremely problematic. I cannot trust
the source code packaging/publishing and merging anymore.
I cannot discern a scenario that leads to these issues but I do have
an image right now where I only changed a single method and the entire
package shows up as ‘changed’.
Anyone experience similar issues?
Johan
