[Seaside] ConfigurationOfSeaside3 not working with Pharo 6 ?
johan at inceptive.be
Tue Jun 13 18:37:00 UTC 2017
I think I fixed the issue in ConfigurationOfSeaside3
Metacello is trying to resolve configurations for previous versions as well (when opening versionner) and when it tries to resolve the packages of 3.1.x, the configuration crashes because it was not adapted for pharo6.
Overall… this is becoming a combinatorial explosion to maintain that config if even older versions need to work on all platforms, so I’m not sure I fixed all issues that are related to this.
In any case, I’m now able to perform the scenario as reported by Cyrille without errors.
Please let me know if you hit any further problems… I’ll try to tackle them, while in the meantime trying to find out how to prevent needing to maintain old versions.
@Mariano, answers to your questions below.
> On 13 Jun 2017, at 18:12, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
> On Tue, Jun 13, 2017 at 12:07 PM, Johan Brichau <johan at inceptive.be <mailto:johan at inceptive.be>> wrote:
> Hi Mariano,
> Seaside 3.2.x works on Gemstone. It was even consolidated to have the same code repository for Gemstone and Pharo from 3.2 onwards: https://travis-ci.org/SeasideSt/Seaside <https://travis-ci.org/SeasideSt/Seaside>
> The github repo https://github.com/SeasideSt/Seaside <https://github.com/SeasideSt/Seaside> is the master for all platforms.
> As for Pharo 6: only Seaside 3.2.2 is working on Pharo 6.
> Ok, so as per above 2 paragraphs, then 3.2.2 should work on Pharo 6.0 and 3.2.x on GemStone. Correct?
> In addition, I made Seaside 3.0.19 work because at Yesplan we are using that version.
> Above you said only 3.2.2 was working on 6.0. But now you said 3.0.19 does too. Can I assume that was released? I am asking just to be sure I understand your answer hahaha.
Yes, it was released.
> I did not look at Seaside 3.1.15 but it should be possible to make the same step as for 3.0.19
> It would be great if someone who needs it can step in there ;)
> Is there an easy way I can see the changes you had to do (in both, Seaside itself and ConfigurationOf)?
> Of course, I can try to make it work. At the least, if it loads/works the "Core", I can test Seaisde plus all the dependencies I use.
I did not have to make a new version of Seaside 3.0.19, because I only had to add 1 method.
The package is Seaside-Pharo60-Legacy and now I also added it to 3.1.6.
Seaside 3.1.6 loads in Pharo6 but there are a couple of remaining failing tests. You probably can fix them by taking a look at the corresponding code in 3.2
If you do, you can send me the packages to integrate and I can probably make a version 220.127.116.11
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside