28 Feb
2010
28 Feb
'10
2:01 a.m.
Dale Henrichs wrote:
When I created the Pier2 configuration I noticed that
'Pier-Pharo-Persistency' has embedded tests that caused a dependency upon
'Pier-Tests-Model'. I seem to remember mentioning it at the time on this list (or
maybe someone else commented)...
In Pier1, it appears the Pier-Security and 'Pier-Squeak-Persistency' also has a
dependency upon Pier-Tests.
In Pier2, Pier-Security has had the tests broken out separately...
Pier2 is fixed now. I split off PRImagePersistencyTest (whose superclass
in in Pier-Tests-Model) into a new Pier-Tests-Pharo-Persistency package.
My build script now does:
Gofer new
renggli: 'pier2';
package: 'Pier-Model';
package: 'Pier-Pharo-Model';
package: 'Pier-Seaside';
package: 'Pier-Pharo-Seaside';
package: 'Pier-Pharo-Persistency';
package: 'Pier-Security';
load.
and, for tests, it also does:
Gofer new
renggli: 'pier2';
package: 'Pier-Tests-Model';
package: 'Pier-Tests-Pharo-Persistency';
package: 'Pier-Tests-Security';
load.