[Seaside-dev] Mason for Seaside 3.0?

[Julian Fitzell]

On Fri, Sep 11, 2009 at 10:00 PM, Dale Henrichs
<dale.henrichs at gemstone.com> wrote:
>
> ----- "Lukas Renggli" <renggli at gmail.com> wrote:
> | > With Metacello, it is also possible to load any one of the groups
> | individually and  then run tests, but to do so would require launching
> | a fresh image 27 times (not to mention the different combinations) ...
> | which is where I assume that Mason comes into play.
> |
> | I don't think that would make sense. What Mason can easily do is to
> | load and run the tests for every build, so that we can provide the
> | test results for every build even if it does not contain the test
> | source.
>
> Groups like Canvas, Session, and Component do not technically depend upon each other but because of the load order, any dependencies that the code in Component may have will be hidden by the fact that it is never loaded by itself (without Session and Canvas preceding it in the load order).

Yup - that would be useful (if somewhat time consuming to run :) ).

Julian