For now I left the package Pier-Security, Pier-Blog,
Pier-Book in the
main repository. These are very big packages and somehow belong to the
core, I thought. But, I am open for discussion.
Pier-Security and Pier-Blog are major components that I plan to integrate
in all my distributions. So, for me, certainly part of the main repository.
Pier-Book is, somehow more specific, although also a major component.
I think security is "core", and a blog and a book are "addons". If
the addon
is big, then it can have its own repository.
I would like to avoid too many repositories.
I only load:
package: 'Pier-Core';
package: 'Pier-Pharo-Core';
package: 'Pier-Model';
package: 'Pier-Pharo-Model';
package: 'Pier-Tests-Model';
package: 'Pier-Seaside';
package: 'Pier-Pharo-Seaside';
package: 'Pier-Security';
package: 'Pier-Pharo-Persistency';
package: 'Pier-Tests-Security';
so I never even noticed that the addon packages were moved.
I just moved them 2 hours ago :-)
I would like to load the tests separately too. IIRC,
there were testcases
whose superclass caused a load dependency. Please add me as developer
(initials: yc), and I'll have a look at it.
What is the problem with the test cases?
I've added you.
Lukas
--
Yanni
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch