[Glass] load ignoring gofer

[Dale K. Henrichs]

Otto,

Okay...the redirects are coming during the load of Grease which is done as a pre-requisite to GLASS1 ... I typically do an upgrade to 1.0-beta.9.1 before loading GLASS1 so the redirectiion happens during that step as Grease is updated in that process ...

So if you make the newer version of Grease available from your third party repos, then the GLASS1 load should be self contained. If you look at the GLASS1 baseline GoferProjectLoader, Grease and XMLSupport still reference external http-based repositories. 

I've got a first cut sample project with a couple of dependent projects, but I just realized that for completeness I should add a Confgiguration-based project that gets locked so I'll have to gen up another dummy project for that ...

Dale
----- Original Message -----
| From: "Otto Behrens" <otto at finworks.biz>
| To: "Dale K. Henrichs" <dale.henrichs at gemtalksystems.com>
| Cc: glass at lists.gemtalksystems.com
| Sent: Monday, November 18, 2013 8:57:15 AM
| Subject: Re: [Glass] load ignoring gofer
| 
| > Don't change the implementation of MetacelloProjectReferenceSpec:)
| 
| Ok, my attempts so for not working.
| 
| > I'm not sure why you are getting the redirected messages ... I
| > don't  get any redirects when I install from github and I don't
| > see any reason why a local repo would behave differently, so I'm
| > curious why this is happening, could you supply with the log files
| > perhaps there are some clues there ...
| 
| Attached...
| 
| Remember I start with the shipped seaside extent.
| 
| the runtime stuff is just loading the ConfigurationOf ...
| 
| > When you say that "you end up calling MetacelloProjectReferenceSpec
| > | loadUsing: aLoader gofer: ignored" are you saying that you are
| > directly calling that method from your own load code, or are you
| > saying that you've traced this method to be the culprit?
| 
| I traced it and ended up there
| 
| Thanks
|