Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

verveinej papers?

by Fabrizio Perin

Hi, are there any publications about VerveinJ that i can cite? Thanks, Fabrizio

13 years, 11 months

Re: Jenkins build is still unstable: moose-latest-dev #415

by Moose

Sounds interesting. I did not see that. Where was it announced? Doru On 7 Jun 2011, at 23:38, Stéphane Ducasse wrote: > did you see what we did with igor today? > we improve the start up so that you can get a much better infrastructure to script image and do not get problem with ui none present? > > On Jun 7, 2011, at 10:43 PM, Alexandre Bergel wrote: > >> I had a look at the failed tests. Many of them are due to what Doru pointed out with opening graphical user interface in a headless mode. Really bad. >> >> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForAllClasses >> • Famix.Tests.Java.VerveineJMooseFinderTest.testMenuEntriesForClasses >> • Moose.Tests.Core.MooseFinderForSimpleNamespacesTest.testMenuEntriesForNamespaces >> • Moose.Tests.Core.MooseFinderForSimplePackagesTest.testMenuEntriesForPackages >> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForClasses >> • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForMethods >> • Moose.Tests.Core.MooseTaskTest.testRunWithProfiler >> >> >> On 7 Jun 2011, at 16:21, admin(a)moosetechnology.org wrote: >> >>> See <http://hudson.moosetechnology.org/job/moose-latest-dev/415/> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >

13 years, 11 months

Re: Jenkins build is still unstable: moose-latest-dev #415

by Moose

All of them, except for the Glamour.Tests.Morphic.GLMFinderMorphicTest.testDefaultFixedSizePanes one are due to the GUI problems in headless mode. I do not know what can be done about it. Cheers, Doru On 7 Jun 2011, at 22:43, Alexandre Bergel wrote: > I had a look at the failed tests. Many of them are due to what Doru pointed out with opening graphical user interface in a headless mode. Really bad. > > • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForAllClasses > • Famix.Tests.Java.VerveineJMooseFinderTest.testMenuEntriesForClasses > • Moose.Tests.Core.MooseFinderForSimpleNamespacesTest.testMenuEntriesForNamespaces > • Moose.Tests.Core.MooseFinderForSimplePackagesTest.testMenuEntriesForPackages > • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForClasses > • Moose.Tests.Core.MooseFinderForSimpleClassesTest.testMenuEntriesForMethods > • Moose.Tests.Core.MooseTaskTest.testRunWithProfiler > > > On 7 Jun 2011, at 16:21, admin(a)moosetechnology.org wrote: > >> See <http://hudson.moosetechnology.org/job/moose-latest-dev/415/> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

13 years, 11 months

graph exploration with guess

by Alexandre Bergel

Cool stuff in it: http://graphexploration.cond.org/ I will work soon on adding a query engine to Mondrian. Quickly finding a node is a graph is important. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 11 months

Fwd: [Pharo-project] Spaktacualr Class Forest of Pharo

by Mariano Martinez Peck

you may be interested ---------- Forwarded message ---------- From: HwaJong Oh <daliot.oh(a)gmail.com> Date: Tue, Jun 7, 2011 at 4:38 AM Subject: [Pharo-project] Spaktacualr Class Forest of Pharo To: pharo-project(a)lists.gforge.inria.fr Hi, I've http://appdal.com/groups/36442/wiki/56611/Pharo__.html rendered all the classes of Pharo into a forest of 3D space with http://appdal.com/groups/36442/wiki/47cf4/Pharo____.html Sketchup Ruby script which was generated by Pharo code. (it does not generate definition of ruby methods. You need to type it :-( ) You can get that code by using Gofer: Gofer new squeaksource: 'DaliotsPlayground'; package: 'ConfigurationOfSketchupRuby'; load. (Smalltalk at: #ConfigurationOfSketchupRuby) project latestVersion load. Best Regards HwaJong Oh -- View this message in context: http://forum.world.st/Spaktacualr-Class-Forest-of-Pharo-tp3578542p3578542.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com. -- Mariano http://marianopeck.wordpress.com

13 years, 11 months

Issue 643 in moose-technology: VerveineJ crashes on a strange invocation

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 643 by tu...(a)tudorgirba.com: VerveineJ crashes on a strange invocation http://code.google.com/p/moose-technology/issues/detail?id=643 Parsing the attached example, produces the below error. I tried to debug this, but I could not figure out where the problem was: 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(Unknown Source) at fr.inria.verveine.extractor.java.VerveineVisitor.visit(Unknown Source) at org.eclipse.jdt.core.dom.ClassInstanceCreation.accept0(ClassInstanceCreation.java:323) 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.ReturnStatement.accept0(ReturnStatement.java:136) 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.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(Unknown Source) 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(Unknown Source) at fr.inria.verveine.extractor.java.VerveineJParser.main(Unknown Source) Attachments: WrongInvocation.java 161 bytes

13 years, 11 months

petit parser ui and position marker

by Norbert Hartl

I really like the petit parser ui to test and fix rule setup. But I'm missing something simple. If I type an example text and select rule and do parse I might get something like end of input expected at 35 Is there a way to see in the example text where position 35 is? That would be useful. Norbert

13 years, 11 months

Issue 611 in moose-technology: VerveineJ does not export all Annotations

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ Milestone-4.4 New issue 611 by tudor.gi...(a)gmail.com: VerveineJ does not export all Annotations http://code.google.com/p/moose-technology/issues/detail?id=611 If you parse Silverpeas-Core, you will get only 17 annotation types: https://github.com/Silverpeas/Silverpeas-Core/zipball/master At least the JUnit 4 annotations are missing.

13 years, 11 months

Issue 642 in moose-technology: Charts legend not working

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 642 by andreho...(a)gmail.com: Charts legend not working http://code.google.com/p/moose-technology/issues/detail?id=642 Legends of charts are not working (due to the change to Pharo 1.3).

13 years, 11 months

Issue 641 in moose-technology: Examples not working

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 641 by andreho...(a)gmail.com: Examples not working http://code.google.com/p/moose-technology/issues/detail?id=641 Some examples/tests are not working due to the change to Pharo 1.3.

13 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev