3.1.4.2-gs

Address the following issues:

• PR #80: Fix Seaside continuation debugging with native code enabled and GemTools
• Compensate for possiblity that $GEMSTONE may not have a trailing / in WAGemStoneRunSeasideGems class>>executeGemCommand:

3.1.4.1-gs

Address the following issues and bugfixes:

• GemStone 3.3 support
• GemServer>>waitForStartGems: calls in tests
• PR #74: Improvements and fixes to WAObjectLog and AJAX Error logging
• Issue #55: Undefined symbols in Gettext for GemStone
• Issue #56: sent but not implemented in Gettext
• Issue #75: PR #74 introduced load order problem

3.1.4-gs

Fixes for the following issues:

• Issue #47: WAGemStoneRunSeasideGems should be able to handle multiple named servers
• Issue #51: failures loading Seaside3.1.3 - need 3.1.3.1 release
• Issue #54: hook in gsApplicationTools ... gemservers for Seaside3
• PR #57: release v3.1.3.2-gs
• Issue #59: Possible random error for FastCGISeasideGemServerTests>>testStartRestartStopServer
• PR #60: Update seasideProcessRequest.adaptor.resultBlock..st
• PR #61: forgot to reference correct version of gsApplicationTools:v1.?...
• Issue #62: Inifinite loop in ZnSeasideNewGemServer>>basicServerOn:
• PR #63: Fix for Issue #62:
• Issue #64: GRGemStonePlatform>>saveLogEntry:shouldCommit: not always safe
• PR #65: fix Issue #64
• Issue #66: result temporary variable shadowed in seasideProcessRequest:adaptor:resultBlock:
• PR #67: alternate fix for issue #60 and also fixes issue #66

3.1.3.1-gs

Only configuration fixes over the 3.1.3 release to ensure correct loading of the correct packages.

3.1.3-gs

v3.1.3-gs

updated v3.1.3-gs (was c7403803f1e35c77e96a10ab72f1de0c9c141fec) for …

3.1.2-gs

v3.1.2-gs

updated v3.1.2-gs (was e0a75590555f9fb6d43b178c4c49475b8b56b121) for …

3.1.1.3-gs31

issues fixed