On 19 February 2013 22:18, phil@highoctane.be <phil@highoctane.be> wrote:
Responses in the text below.
2013/2/19 Frank Shearar <frank.shearar@gmail.com>:
On 19 February 2013 20:51, phil@highoctane.be <phil@highoctane.be> wrote:
Got this thing biting me while testing the relase:
I added a project of mine from the ss3.gemstone.com system and the Monticello registration over there says:
MCHttpRepository location: 'http://ss3.gemstone.com/ss/HO-Experiments' user: 'PBK' password: ''
I add that into Pharo as a ss3 repository.
There I am asked for:
MCGemstoneRepository location: 'http://ss3.gemstone.com/ss/' user: '' password: ''
Where/what is "there"? Something's prompting you to fill in repository details and autofilled it with an MCGemstoneRepository declaration?
Where is in Pharo 2.0 Monticello when adding an SS3 repository. That's what the text editor area contains as default text.
I didn't noticed the MCGemstoneRepository instead of MCHttpRepository and copy/pasted as usual.
Then, error.
Took a minute to see why and get my mcz back.
So, either SS3 has to change the registration information or Pharo does something weird with SS3. I don't know.
Guess I need to put things in SmalltalkHub :-)
Well, ss3 is just an HTTP Monticello repository service. It's not ss3's fault that something else mentioned MCGemstoneRepository.
As long as both would work, it would be a non issue. But using MCHttpRepository location: 'http://ss3.gemstone.com/ss/HO-Experiments' user: 'PBK' password: ''
fails miserably in Pharo 2.0. That's why I had to change it to MCGemstoneRepository for it to work.
So, either ss3 isn't just an HTTP Monticello repository service or Pharo 2.0 introduced something special... I don't know.
How very odd. I _always_ use MCHTTPRepository when accessing ss3 projects. frank
frank
Phil