Moose-dev October 2014

moose-dev@list.inf.unibe.ch

44 participants
133 discussions

Build failed in Jenkins: moose-5.0 #2783

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/2783/> ------------------------------------------ Started by timer Started by upstream project "fame" build number 599 originally caused by: Started by timer Started by upstream project "graph-et" build number 843 originally caused by: Started by timer Started by upstream project "graph-et2" build number 225 originally caused by: Started by timer Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-5.0/ws/> Deleting project workspace... done [moose-5.0] $ /bin/sh -xe /tmp/hudson4629044904692084774.sh + wget --quiet -O - http://get.pharo.org/30+vmLatest + bash Downloading the latest 30 Image: http://files.pharo.org/image/30/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/latest.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Downloading PharoV30.sources: http://files.pharo.org/sources//PharoV30.sources.zip Creating starter scripts pharo and pharo-ui + ./pharo Pharo.image save moose-5.0 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-5.0.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development 'Installing ConfigurationOfMoose development' [31mError: Could not access http://smalltalkhub.com/mc/Moose/Moose/main/: ZnHttpUnsuccessful: 503 Service Temporarily Unavailable [0mMCSmalltalkhubRepository(Object)>>error: MCSmalltalkhubRepository>>loadAllFileNames in Block: [ :exception | self error: 'Could not access ' , s...etc... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ZnHttpUnsuccessful(Exception)>>signal ZnClient>>handleResponse ZnClient>>executeWithRedirectsRemaining: ZnClient>>executeWithRetriesRemaining: in Block: [ self executeWithRedirectsRemaining: self maxNumb...etc... BlockClosure>>on:do: ZnClient>>executeWithRetriesRemaining: ZnClient>>executeWithTimeout in Block: [ self executeWithRetriesRemaining: self numberOfR...etc... BlockClosure>>on:do: ZnClient>>executeWithTimeout in Block: [ ... ZnClient>>withTimeoutDo: in Block: [ ^ block value ] ZnConnectionTimeout(DynamicVariable)>>value:during: in Block: [ ... BlockClosure>>ensure: ZnConnectionTimeout(DynamicVariable)>>value:during: ZnConnectionTimeout class(DynamicVariable class)>>value:during: ZnClient>>withTimeoutDo: ZnClient>>executeWithTimeout ZnClient>>execute in Block: [ result := self executeWithTimeout ] ZnClient>>withProgressDo: in Block: [ ^ block value ] ZnSignalProgress(DynamicVariable)>>value:during: in Block: [ ... BlockClosure>>ensure: ZnSignalProgress(DynamicVariable)>>value:during: ZnSignalProgress class(DynamicVariable class)>>value:during: ZnClient>>withProgressDo: [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

9 years, 6 months

Smalltalk Devroom at FOSDEM 2015: Call for Participation

by Stephan Eggermont

Call for Participation in the Smalltalk Devroom at FOSDEM 2015. http://www.fosdem.org, please forward " A devroom for the Pharo, Squeak, Amber, GST, Etoilé, Seaside, Moose Smalltalk projects & Objective Smalltalk and Newspeak as derived languages. Smalltalk environments offer a very high development productivity, unmatched by their successors. Come do some pair programming with us and experience yourself the advantages of a real OO environment" The meetup will take place Sunday, February 1, 2015, room S.H.2214. This room has 100 seats, a VGA video projector and wireless internet. Presentations will be video recorded (CC BY). Proposals on content and format are welcome. HOW TO SUBMIT: All submissions are made in the Pentabarf event planning tool at https://penta.fosdem.org/submission/FOSDEM15 When submitting your talk in Pentabarf, make sure to select the 'Smalltalk devroom' as the 'Track'. If you already have an account there, please reuse it. QUESTIONS & VOLUNTEERS Any questions, and video volunteers, please mail to stephan[@]stack[dot]nl with [FOSDEM] in the subject. I will send out updates on a regular basis to the lists and anyone stating his interest. PLANNED SCHEDULE: Sessions of 30/60 minutes (-5 min setup), last session a two hour hands-on introduction to smalltalk. First session or lunch session can be show-us-your-project, lightning talks. The desired time slot is meant to help you prevent conflicts with other dev rooms in which you might have a talk or your travel arrangements. There are alternative, non smalltalk-specific tracks available: lightning talk and the main track Please submit before December 1, 23:00 GMT+1. Devroom related URLs: http://www.pharo.org http://www.squeak.org/ http://etoileos.com/ http://www.seaside.st/ http://smalltalk.gnu.org/ http://www.moosetechnology.org http://amber-lang.net http://newspeaklanguage.org/ http://http://objective.st http://www.esug.org FOSDEM is the Free and Open source Software Developers' European Meeting, a free and non-commercial two-day weekend event that offers open source contributors a place to meet, share ideas and collaborate.

9 years, 6 months

Issue 1087 in moose-technology: Migrate Overview Pyramid to RTView

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Finder New issue 1087 by tu...(a)tudorgirba.com: Migrate Overview Pyramid to RTView https://code.google.com/p/moose-technology/issues/detail?id=1087 I removed Overview Pyramid from the MooseModel menu. It is still in the image. It would be great if anyone would want to refactor this. In doing so, you should use directly RTView and compose the boxes manually rather than going through the MondrianBuilder. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 6 months

how to handle generic methods in Famix 3.0

by Thomas Haug

Hi everybody, I hope my question is not off topic: I am currently trying to figure out how to describe generic methods in Famix 3.0 (for the .NET FamixGenerator) For example in Java you can write the following code. public class ClassWithGenericMethod { public static <TResult> TResult getTheGeneric(String resource) { return null; } public static <TValue> void useTheGeneric(TValue value) { System.out.println("value '"+value +"' type: "+value.getClass()); } If I run InFamix on this code I get an Famix file containing something like: 1 method: (FAMIX.Method (id: 24) (sourceAnchor (ref: 60)) (parentType (ref: 30)) (declaredType (ref: 33)) (name 'getTheGeneric') (signature 'getTheGeneric(_unknown_path::String)') (hasClassScope true) (isPublic true) (isPureAccessor true) (ATFD 0.00) (ALD 0.00) (CYCLO 1.00) (DR 0.00) (ICDO 1.00) (ICIO 1.00) (LOC 3.00) (LOCOMM 1.00) (LDA 1.00) (MAXNESTING 1.00) (NOAV 0.00) (NOOC 0.00) (NOPAR 1.00) (OCDO 0.00) (OCIO 0.00) ) But id 33 is not existing. 2 method: (FAMIX.Method (id: 25) (sourceAnchor (ref: 61)) (parentType (ref: 30)) (declaredType (ref: 28)) (name 'useTheGeneric') (signature 'useTheGeneric(_unknown_path::TValue)') (hasClassScope true) (isPublic true) (ATFD 0.00) (ALD 0.00) (CYCLO 1.00) (DR 0.00) (ICDO 1.00) (ICIO 1.00) (LOC 3.00) (LOCOMM 1.00) (LDA 1.00) (MAXNESTING 1.00) (NOAV 2.00) (NOOC 2.00) (NOPAR 1.00) (OCDO 0.00) (OCIO 0.00) ) (FAMIX.Parameter (id: 35) (name 'value') (parentBehaviouralEntity (ref: 25)) (declaredType (ref: 36)) (position 0) ) But id 36 is not existing. I am wondering if there should be something like ParameterizableMethod (like ParameterizableClass? Can anybody give me some clues? Thank you very much Thomas ----------- Thomas Haug Principal Consultant MATHEMA Software GmbH Anschrift: Henkestraße 91 91052 E r l a n g e n Telefon: 09131/8903- 0 Telefax: 09131/8903-55 E-Mail: thomas.haug(a)mathema.de Internet: http://www.mathema.de Handelsregister: HR B 8965, Fürth/Bayern Geschäftsführer: Michael Wiedeking Andreas Hanke

9 years, 6 months

Did you publish the import customisation we did?

by stepharo

Hi for certain analyses we found difficult that the subclasses of a classes get automatically imported so we introduce a setting to control this aspect. We modified the importer and the wizard. Anne did you publish the code? STef

9 years, 6 months

How to annotating a moose model?

by Alexandre Bergel

Hi! We would like to annotate elements of a moose model with some metric values. For example, embedding the result of a test coverage within a moose model. Programmatically, I can use propertyNamed: name put: value on any moose entity. That is great. However, I cannot export it in a MSE file. How to do this? I have tried the annotation pane: But I am not sure how it works. Saving to a MSE file does not seem to keep the value I enter in the annotation. Any hint on how to save annotation in a mse file? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 6 months

permanent researcher positions at lille

by Stéphane Ducasse

Hi guys it is probable that there will be two permanent researcher positions at Lille. one for Prof level (either to work with us or to create a separate group in the mid term) one for associate prof level. These positions are really cool. Pass the information around. People can contact me for further information. Stef

9 years, 6 months

Analyzing database

by Alexandre Bergel

Hi! I am wondering if any of you is using Roassal and/or Moose to analyze data bases? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 6 months

Issue 1091 in moose-technology: Moose finder actually depends on gt-inspector but not its configuration

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1091 by damien.c...(a)gmail.com: Moose finder actually depends on gt-inspector but not its configuration https://code.google.com/p/moose-technology/issues/detail?id=1091 On Pharo 3, loading Moose with spec className: #ConfigurationOfMoose; loads: #('UI' 'Core' 'PetitMSE' 'Moose-Wizard'); loads Object>>mooseFinderMetaIn: whose code mooseFinderMetaIn: composite <moosePresentationOrder: 1000> (self mooseInterestingEntity gtInspectorMetaIn: composite) titleIcon: MooseIcons mooseMethodsBrowser depends on #gtInspectorMetaIn: that is not in the image. You can download a problematic image at https://ci.inria.fr/rmod/job/Boa. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

9 years, 6 months

TRLineShape>>includesPoint:

by Peter Uhnák

Hi Alex, would it be possible to allow specification of epsilon for TRLineShape>>includesPoint:? Having it small makes sense if it is processed by machine, but trying to click on it by hand is hard. Alternatively I could subclass it in my program but then I would have to change it also in all RTLabel subclasses. Or is there better way? Changing the epsilon seems most straightforward to me. Peter

9 years, 6 months

← Newer
1
...
5
6
7
8
9
10
11
...
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2014