-
Notifications
You must be signed in to change notification settings - Fork 2
GemStone update #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
add Pharo32-8.0
add Pharo32-8.0 to travis.yml
Cleanup: Remove ConfigurationOfBitmapCharacterSet
Cleanups like formatting and lint checking
Remove BitmapCharacterSet class>>#inspectorClass
…itmapCharacterSetTestassertSetcopiedFromequals-should-use-isNotNil BitmapCharacterSetTest>>#assertSet:copiedFrom:equals: should use isNotNil
Cleanup: Remove ConfigurationOfBitmapCharacterSet
Cleanups like formatting and lint checking
Remove BitmapCharacterSet class>>#inspectorClass
…itmapCharacterSetTestassertSetcopiedFromequals-should-use-isNotNil BitmapCharacterSetTest>>#assertSet:copiedFrom:equals: should use isNotNil For GemStone: - changed the category to match the Pharo one - renamed -Core to -Base package to match the upstream - ignoring manifest changes - ignoring symbols->string changes as this was already done
|
@dalehenrich I have update the CI according to your request(s). Your original comments are in closed PR as I have tried some workflows. This caused the original PR to be closed. Here is the original comment link |
|
There were three failing tests: Now everything passes (only Post Workflow Status To Slack fails) as I have created GemStone compatible code. If PharoCompatibility (GsPharo) is loaded the tests started to pass without any modification. You probably do not want to introduce new dependency on PharoCompatibility. How do you deal with such situation? I want to know for future reference in more complex situations. |
|
I have noticed the |
I added as an example of using a .solo script to read Rowan Project definitions and write the project as a .gs file ... so it doesn't need to be updated |
I think that first order you do as you did and change the code to be compatible with GemStone ... if the changes are too widespread, then adding a gemstone-specific dependency to another baseline is the best answer ... |
No description provided.