[Pharo-project] Issue 3601 in pharo: Recommended Seaside version in Pharo-1.2 outdated
Status: Accepted Owner: Torsten....@astares.de CC: renggli, philippe...@gmail.com, marianopeck, stephane...@gmail.com, da...@teleport.com, marcus.d...@gmail.com Labels: Milestone-1.2-DevImage New issue 3601 by Torsten....@astares.de: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 Use a prebuilt Pharo 1.2 from the hudson server. When you run "DEVImageWorkspaces openExternalProjectWorkspace" it is suggested to load ConfigurationOfSeaside30 and load ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.0-alpha5.15') load. it comes up with: "Deprecation: The method SmalltalkImage platformName has been deprecated. Use Smalltalk os platformName" Thats not nice for newbees ;) We should also check the other recommended load scripts ... QUESTION: I think a newer version of Seaside like 3.0.3 would help ... Can anyone confirm that Seaside 3.0.3 is OK for Pharo-dev 1.2
Comment #1 on issue 3601 by Torsten....@astares.de: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 Seaside loads and runs when I use the 3.0.3 version: ((Smalltalk at: #ConfigurationOfSeaside30) project version: '3.0.0-alpha5.15') load. but I get 5 failing tests (WAFileLibraryTest and WAPharoFileLibraryTest fail) since GRPharoPlatform>>useByteArrayLiterals uses "Preferences": useByteArrayLiterals "whether ByteArray literals can/should be used" ^Preferences valueOfFlag: #compileUseNewCompiler ifAbsent: [ false ] and there is WAPharoLibraryTest>>hasNewCompiler too: hasNewCompiler Preferences valueOfFlag: #compileUseNewCompiler ifAbsent: [ ^false ]. ^true and there is a (IMHO redundant) WAPharoLibraryTest>>compileUseNewCompiler: compileUseNewCompiler ^Preferences valueOfFlag: #compileUseNewCompiler ifAbsent: [ false ]
Comment #2 on issue 3601 by johanbri...@me.com: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 I fixed this already in #3540
Comment #3 on issue 3601 by Torsten....@astares.de: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 Yes, but it looks like your fix ("ImageForDevelopers-pharo-JohanBrichau.248") was not yet integrated into ConfigurationOfPharo. Fixed in ConfigurationOfPharo-tbn.128
Updates: Status: Closed Comment #4 on issue 3601 by marcus.d...@gmail.com: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 in build #99
participants (1)
-
pharo＠googlecode.com