-
Notifications
You must be signed in to change notification settings - Fork 68
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
onUpgrade option for loading project #371
Comments
I don't think there's an option for this yet. Would you like to add it? :) |
Another idea: should not it be default behaviour? |
@dalehenrich what do you think? Should we make it the default? And will we still need an option to turn it off? |
According to README, this is already supported as an option of However, we tested it in Roassal3+Pharo9 in the same situation that @dionisiydk when reported the issue and the problem wasn't fixed. Not sure 100% what happened but went for other solution. |
Thanks for the update, @tinchodias. What "other solution" did you go for? If you could provide some steps to reproduce, we could run smalltalkCI in headful mode and debug the run. |
That "other solution" was to create preloading .st script that sends I think this is not a bug of smalltalk-ci but Metacello. I say that because when Roassal3 is loaded using The new packages are loaded correctly only if I click on "Load". The same dialogs appears when you load Metacello without BTW, I just discovered (thanks @akevalion), handling a warning in the following way makes loading work as expected: [Metacello new
baseline: 'Roassal3';
repository: 'github://ObjectProfile/Roassal3';
load ] on: MCMergeOrLoadWarning do: [:warning | warning load ] (it loads the code and there is no UI asking anything). |
Hi.
I can't find what to put in ston file to tell metacello:
Is it possible?
Now Calypso is in Pharo 7. And CI does not really loads code because it is already inside Pharo.
The text was updated successfully, but these errors were encountered: