Moose-dev May 2011

moose-dev@list.inf.unibe.ch

33 participants
186 discussions

by Matthias Junker

Hey, i tried to load a project with verveinej.sh and get a NullPointerException. I only provided the path to the sources as an argument: Exception in thread "main" java.lang.NullPointerException at org.eclipse.jdt.core.dom.MethodBinding.isAnnotationMember(MethodBinding.java:55) at fr.inria.verveine.extractor.java.VerveineVisitor.methodInvocation(VerveineVisitor.java:554) at fr.inria.verveine.extractor.java.VerveineVisitor.visit(VerveineVisitor.java:497) at org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:237) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551) at org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:245) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528) at org.eclipse.jdt.core.dom.VariableDeclarationFragment.accept0(VariableDeclarationFragment.java:225) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551) at org.eclipse.jdt.core.dom.VariableDeclarationStatement.accept0(VariableDeclarationStatement.java:273) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551) at org.eclipse.jdt.core.dom.Block.accept0(Block.java:136) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528) at org.eclipse.jdt.core.dom.TryStatement.accept0(TryStatement.java:195) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551) at org.eclipse.jdt.core.dom.Block.accept0(Block.java:136) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2528) Disconnected from the target VM, address: '127.0.0.1:51367', transport: 'socket' at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:504) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2551) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:219) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2480) at fr.inria.verveine.extractor.java.FamixRequestor.acceptAST(FamixRequestor.java:31) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:1016) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:628) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:982) at fr.inria.verveine.extractor.java.VerveineJParser.parse(VerveineJParser.java:169) at fr.inria.verveine.extractor.java.VerveineJParser.main(VerveineJParser.java:153) This is the MethodBinding where i get the NullPointer: • this = {org.eclipse.jdt.core.dom.MethodBinding@1077}"public java.lang.String getName() " • binding = {org.eclipse.jdt.internal.compiler.lookup.ParameterizedMethodBinding@1808}"public java.lang.String getName() " • resolver = {org.eclipse.jdt.core.dom.DefaultBindingResolver@1809} • parameterTypes = null • exceptionTypes = null • name = null • declaringClass = null • returnType = null • key = null • typeParameters = null • typeArguments = null • annotations = null • parameterAnnotations = null Did anybody have similar problems? Cheers Matt

12 years, 11 months

Non-valid MSE files

by Serge Stinckwich

Hi all, i try several meta-models available here with the MSE format: http://www.emn.fr/z-info/atlanmod/index.php/AtlanticFM3 This is very nice to be able to load them in MOOSE! Some of them like ACME 1.2: http://gforge.inria.fr/scm/viewvc.php/*checkout*/AtlanticFM3/ACME.mse?root=… are in fact non-valid MSE files and could not be loaded in MOOSE, because they used multi-inheritance and FM3 meta-model define only single inheritance between classes. There is also others problems of conformance to MSE with some files but i didn't have too much time to investigate. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

12 years, 11 months

Glamour: error when title is nil

by Veronica Isabel Uquillas Gomez

Hi Doru, I am having a problem with Glamour. When a presentation has titleIcon instead of title an error appears because its text is nil. You can reproduce the problem with: GLMBasicExample>>tabsWithDifferentLabels This is happening in certain images: PharoDev 1.2.1, PharoCore 1.3, PharoDev 1.3 I was imagining that in 1.3 is normal as I couldn't run many examples. But then why is failing in PharoDev 1.2.1? Regards, Veronica

12 years, 11 months

Issue 613 in moose-technology: Glamour presentation rendering raises an error when title is nil

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.4 New issue 613 by tudor.gi...(a)gmail.com: Glamour presentation rendering raises an error when title is nil http://code.google.com/p/moose-technology/issues/detail?id=613 When a presentation has titleIcon instead of title an error appears because its text is nil. You can reproduce the problem with: GLMBasicExample>>tabsWithDifferentLabels

12 years, 11 months

"Clean Up Your Mess - A guide to visual design for everybody"

by Alexandre Bergel

Easy rules on graphic design: http://www.visualmess.com/ Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 11 months

documentation effort of Mondrian

by Alexandre Bergel

Hi! I recently documented the source code of Mondrian. This means adding class comments and methods comments. Before the effort, only 14% of the methods were commented. Below a screenshot of the DocumentationBlueprint, a visualization intended to help me document. The MOShape class hierarchy is here presented. After the effort, 24% of the methods are commented. Here is another screen, after 3 days of work. Here is the legend: 'big box = class' . 'edge = inheritance link' . 'small box = method' . 'small box height = number of lines of code' . 'small box width = number of collaborating classes' . 'red border = non commented' . Comments are welcome Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 11 months

Re: Issue 596 in moose-technology: Name of the project not set when importing from Smalltalk

by moose-technology＠googlecode.com

Updates: Summary: Name of the project not set when importing from Smalltalk Labels: Component-Finder Comment #2 on issue 596 by tudor.gi...(a)gmail.com: Name of the project not set when importing from Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=596 I took a look and it seems to be related to TextMorph, or at least the way it is setup. If you accept the text, it the name is properly set. I do not know how to setup the TextMorph not to require an accept. Cyrille?

12 years, 11 months

Issue 607 in moose-technology: inFusion should make AnnotationInstanceAttribute>>annotationTypeAttribute point to AnnotationTypeAttribute

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 607 by tudor.gi...(a)gmail.com: inFusion should make AnnotationInstanceAttribute>>annotationTypeAttribute point to AnnotationTypeAttribute http://code.google.com/p/moose-technology/issues/detail?id=607 Currently it points to the declaredType.

12 years, 11 months

Project moose-on-moose

by Andre Hora

Hello Doru, I saw you are generating a Moose On Moose Report.xml<http://hudson.moosetechnology.org/job/moose-on-moose/lastSuccessfulBuild/ar…>report. Is it SmallLint rules? Is the code (to generate this report) provided by Moose? thanks and regards, -- Andre Hora

12 years, 11 months

Issue 604 in moose-technology: VerveineJ should export in UTF-8

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 604 by tudor.gi...(a)gmail.com: VerveineJ should export in UTF-8 http://code.google.com/p/moose-technology/issues/detail?id=604 The MSE file format should be always in UTF-8.

12 years, 12 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev May 2011