Hi Paul,
Best way to handle this is to upgrade all configurations to use ConfigurationOfSeaside3. If this is not an options, you should use the Metacello scripting api. Here you have the possibility to disallow loading of Seaside30, since this loads from the wrong location and the wrong versions.
Cheers,
Diego
On Oct 31, 2013, at 8:38 PM, Paul DeBruicker wrote:
> Hi -
>
> I have some sub-projects that use ConfigurationOfSeaside30 #stable. I include those in projects that use the new ConfigurationOfSeaside3. If ConfigurationOfSeaside3 has loaded Seaside version 3.0.9 into an image, those sub-projects that specify ConfigurationOfSeaside30 seem to also load Seaside version 3.0.8 later on in the build.
>
>
> Is anyone else noticing this in their projects?
>
> If so how are you handling it?
>
> Thanks
>
> Paul_______________________________________________
> seaside mailing list
>
[hidden email]
>
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
