On smalltalkhub, Moose/PetitParser And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/ Stephan
Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems) ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
It loads #development as any CI job should do. Doru On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems)
----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com "Every thing has its own flow"
I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do. Norbert
Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor@tudorgirba.com>:
It loads #development as any CI job should do.
Doru
On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean@clipperadams.com> wrote: Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems)
----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com
"Every thing has its own flow"
In the case of Moose, #development and #bleedingEdge are the same. Doru On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert@hartl.name> wrote:
I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do.
Norbert
Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor@tudorgirba.com>:
It loads #development as any CI job should do.
Doru
On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems)
----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
I load it from the moose team on sth. Works for me, browser included. Le 18 juil. 2014 09:24, "Tudor Girba" <tudor@tudorgirba.com> a écrit :
In the case of Moose, #development and #bleedingEdge are the same.
Doru
On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert@hartl.name> wrote:
I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do.
Norbert
Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor@tudorgirba.com>:
It loads #development as any CI job should do.
Doru
On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean@clipperadams.com> wrote:
Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems)
----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Hi, This is a question for the moosers :) Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella? cheers, Esteban On 18 Jul 2014, at 10:00, phil@highoctane.be wrote:
I load it from the moose team on sth. Works for me, browser included.
Le 18 juil. 2014 09:24, "Tudor Girba" <tudor@tudorgirba.com> a écrit : In the case of Moose, #development and #bleedingEdge are the same.
Doru
On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert@hartl.name> wrote: I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do.
Norbert
Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor@tudorgirba.com>:
It loads #development as any CI job should do.
Doru
On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean@clipperadams.com> wrote: Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems)
----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Because nobody did it. Doru On Fri, Jul 18, 2014 at 12:04 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
This is a question for the moosers :) Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella?
cheers, Esteban
On 18 Jul 2014, at 10:00, phil@highoctane.be wrote:
I load it from the moose team on sth. Works for me, browser included. Le 18 juil. 2014 09:24, "Tudor Girba" <tudor@tudorgirba.com> a écrit :
In the case of Moose, #development and #bleedingEdge are the same.
Doru
On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert@hartl.name> wrote:
I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do.
Norbert
Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor@tudorgirba.com>:
It loads #development as any CI job should do.
Doru
On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean@clipperadams.com
wrote:
Stephan Eggermont wrote
And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/
Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems)
----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com <http://nabble.com/>.
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
participants (6)
-
Esteban Lorenzano -
Norbert Hartl -
phil＠highoctane.be -
Sean P. DeNigris -
Stephan Eggermont -
Tudor Girba