23 Dec
2013
23 Dec
'13
6:07 p.m.
Just do it:
Gofer new smalltalkhubUser: 'ronsaldo' project: 'roassal3d'; package:
'ConfigurationOfRoassal3d'; load. (Smalltalk at: #ConfigurationOfRoassal)
loadDevelopment
Alexandre
On Dec 23, 2013, at 4:56 PM, Ben Coman <btc(a)openInWorld.com> wrote:
Serge Stinckwich wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Apparently there is no CI job on
https://ci.inria.fr/pharo-contribution/
in order to use PharoLauncher.
Regards
On Thu, Dec 19, 2013 at 4:17 PM, Stephan Eggermont
<stephan(a)stack.nl>
wrote:
You mean something other than [1] & [2]. The first builds immediately on any
source or upstream change. The latter is triggered manually for a significant release to
turn it into a deployed application.
[1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher
[2] https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Is there a configuration that works in Moose 5?
Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev