Yes, from the Configuration Browser. You have Roassal 3d
Alexandre
On Dec 19, 2013, at 4:17 PM, Stephan Eggermont stephan@stack.nl wrote:
Is there a configuration that works in Moose 5?
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@stack.nl wrote:
Is there a configuration that works in Moose 5?
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@openInWorld.com wrote:
Serge Stinckwich wrote:
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@stack.nl wrote:
Is there a configuration that works in Moose 5?
Stephan _______________________________________________ Moose-dev mailing list
Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Sorry Ben,
I was talking about a ROASSAL 3D image that I can see under PharoLauncher list of images.
Regards,
On Mon, Dec 23, 2013 at 4:56 PM, Ben Coman btc@openinworld.com wrote:
Serge Stinckwich wrote:
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@stack.nl wrote:
Is there a configuration that works in Moose 5?
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Currently we do not have it. But it would be great to have one. I will try to create one...
Alexandre
On Dec 24, 2013, at 12:12 PM, Serge Stinckwich serge.stinckwich@gmail.com wrote:
Sorry Ben,
I was talking about a ROASSAL 3D image that I can see under PharoLauncher list of images.
Regards,
On Mon, Dec 23, 2013 at 4:56 PM, Ben Coman btc@openinworld.com wrote:
Serge Stinckwich wrote:
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@stack.nl wrote:
Is there a configuration that works in Moose 5?
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Thank you Alex. Not really urgent at the moment ! Enjoy hollydays ;-) Happy Christmas
On Wed, Dec 25, 2013 at 9:17 AM, Alexandre Bergel alexandre.bergel@me.com wrote:
Currently we do not have it. But it would be great to have one. I will try to create one...
Alexandre
On Dec 24, 2013, at 12:12 PM, Serge Stinckwich serge.stinckwich@gmail.com wrote:
Sorry Ben,
I was talking about a ROASSAL 3D image that I can see under PharoLauncher list of images.
Regards,
On Mon, Dec 23, 2013 at 4:56 PM, Ben Coman btc@openinworld.com wrote:
Serge Stinckwich wrote:
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@stack.nl wrote:
Is there a configuration that works in Moose 5?
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Ben Coman -
Serge Stinckwich -
Stephan Eggermont