On 14-01-16 10:57, Blondeau Vincent wrote:
I just solved the bug that appears on Pharo 5, updated the configuration
and uploaded it to the catalogs.
It should work now.
Thanks Vincent.
It would be better if the problem were fixed in
ConfigurationOfXMLParser. It misses the #'pharo4.x' and #common parts
(or possibly #'pharo5.x') and the #release based versioning is not up to
date.
I would expect to be able to depend on #'release-2' in
ConfigurationOfPharoLauncher. I would expect #'release-2' to point to
#'release-2.5' which would point to 2.5.6 for #'pharo4.x' and 2.5.7 for
#'pharo5.x'
The dependency on Ston, JSON and OSProcess would be safe to be on #stable
Stephan
