Re: Loading Seaside in fresh pharo 4

Lyn Headley <[email protected]>
Newsgroups gmane.comp.lang.smalltalk.squeak.seaside
Message-ID <CAGsKgxx7ehcY_9JNkVT5bp5yzNH8jhDzh_-XBaNdkZ8V4NzdUw@mail.gmail.com>
Still on this topic, sort of. My real goal is to create a nice Metacello
configuration for my project so I can easily load it into a fresh pharo or
Gemstone install. Currently getting a _different_ stack trace (looks like a
lower level one, not a regular debugger) when I try to load the
configuration into a fresh pharo 4 image. Do you see anything wrong with
this piece where I define project 'Seaside3'?

spec
project: 'Seaside3'
with: [
spec
className: 'ConfigurationOfSeaside3';
versionString: #stable;
loads: #('default');
repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'
].


Or perhaps something else is wrong with my Configuration? I have enclosed
the complete Metacello Configuration I am building as well as the stack
trace.

baseline02: spec
"
(ConfigurationOfZDialog project version: '0.2-baseline') load.
"

<version: '0.2-baseline'>
spec
for: #common
do: [
spec blessing: #baseline.
spec repository: 'filetree:///home/laheadle/smalltalk/zdialog'.
spec
project: 'Seaside3'
with: [
spec
className: 'ConfigurationOfSeaside3';
versionString: #stable;
loads: #('default');
repository: 'http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'
].
spec
project: 'PetitParser'
with: [
spec
className: 'ConfigurationOfPetitParser';
versionString: #stable;
loads: #('default');
repository: 'http://source.lukas-renggli.ch/petit' ].
spec
package: 'ZDialog-Core';
package: 'ZDialog-CAD';
package: 'ZDialog-Parser' with: [ spec requires: 'PetitParser' ];
package: 'ZDialog-Core-Tests' with: [ spec requires: 'ZDialog-Core' ];
package: 'ZDialog-Web' with: [ spec requires: #('Seaside3' 'ZDialog-Core')
] ]


------


MessageNotUnderstood: Array>>nsWriteStream
Array(Object)>>doesNotUnderstand: #nsWriteStream
Array(Collection)>>flatCollect:
Array(Collection)>>gather:
ProtocolOrganizer>>allMethods
AllProtocol>>methods
AllProtocol>>name
ProtocolOrganizer>>classify:inProtocolNamed:
ProtocolOrganizer>>classify:inProtocolNamed:suppressIfDefault:
ClassOrganization>>classify:under:suppressIfDefault:
ClassOrganization>>classify:under:
[ myClass organization classify: selector under: category ] in
MethodAddition>>notifyObservers in Block: [ myClass organization classify:
selector under: c...etc...
BlockClosure>>ensure:
SystemAnnouncer>>suspendAllWhile:
MethodAddition>>notifyObservers
[ :each | each notifyObservers ] in
MCMultiPackageLoader(MCPackageLoader)>>basicLoadDefinitions in Block: [
:each | each notifyObservers ]
OrderedCollection>>do:
MCMultiPackageLoader(MCPackageLoader)>>basicLoadDefinitions
[ self basicLoadDefinitions ] in [ self handleLoadErrorsDuring: [ self
basicLoadDefinitions ] ] in
MCMultiPackageLoader(MCPackageLoader)>>basicLoad in Block: [ self
basicLoadDefinitions ]
BlockClosure>>on:do:
[
aBlock
on: InMidstOfFileinNotification
do: [ :notification | notification resume: true ] ] in
MCMultiPackageLoader(MCPackageLoader)>>handleLoadErrorsDuring: in Block: [
...
BlockClosure>>on:do:
MCMultiPackageLoader(MCPackageLoader)>>handleLoadErrorsDuring:
[ self handleLoadErrorsDuring: [ self basicLoadDefinitions ] ] in
MCMultiPackageLoader(MCPackageLoader)>>basicLoad in Block: [ self
handleLoadErrorsDuring: [ self basicLoadDef...etc...
BlockClosure>>ensure:
MCMultiPackageLoader(MCPackageLoader)>>basicLoad
[ self basicLoad ] in
MCMultiPackageLoader(MCPackageLoader)>>loadWithNameLike: in Block: [ self
basicLoad ]
BlockClosure>>ensure:
MCMultiPackageLoader(MCPackageLoader)>>useChangeSetNamed:during:
MCMultiPackageLoader(MCPackageLoader)>>useNewChangeSetNamedLike:during:
MCMultiPackageLoader(MCPackageLoader)>>loadWithNameLike:


On Fri, Oct 16, 2015 at 7:16 AM, Johan Brichau <[email protected]> wrote:

>
> On 16 Oct 2015, at 10:33, Sven Van Caekenberghe <[email protected]> wrote:
>
>
> On 16 Oct 2015, at 09:14, Johan Brichau <[email protected]> wrote:
>
> Mind that ‘default’ is a very small set for Seaside 3.1
>
> See the configuration’s groups for more packages.
>
>
> What is the recommended group for beginners then ?
>
>
> I just published a new ConfigurationOfSeaside3 with a ‘OneClick’ group for
> current Seaside 3.1
>
> Should have thought about that question before though….
>
> cheers
> Johan
>
> _______________________________________________
> seaside mailing list
> [email protected]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>

_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.