Thomas Degueule

You are right. We include the impact of `@Deprecated` elements as it may give a better idea of which clients will be faced with a deprecated API. Thanks for your...

> Spoon should currently compare types by considering them in isolation, detached from the rest of the model This makes sense and explains this behavior. > But the wrapper was...

Picking whichever JDT version is currently installed in Eclipse (current behavior) implies that the behavior of Rascal programs changes according to where/who runs them. It should be fixed, i.e. we...

It doesn't matter which project I run the Rascal console on (`rascal`, `rascal-eclipse`, `some-rascal-project`, or no project at all): it resolves the JDT bundle in all cases.

Actually this is more of a `rascal-eclipse` issue. The issue is probably around [those lines](https://github.com/usethesource/rascal-eclipse/blob/master/rascal-eclipse/src/org/rascalmpl/eclipse/nature/ProjectEvaluatorFactory.java#L497-L523): the resulting classpath mixes `rascal.jar` with the bundles of the current Eclipse installation; there should...

Diving a little deeper, it turns out that `rascal-eclipse` itself declares an *unversioned* MANIFEST.MF dependency towards `org.eclipse.jdt` (it needs it @ run time to use the `JavaCore` utilities and parse...

Seems like it's definitely an issue on our side; I'll investigate.

ebc556aa48d567b321800aa90c834e945fb0ac99 should hopefully fix the issue.

COCOMO is a software cost estimation model (cf. [COCOMO](https://en.wikipedia.org/wiki/COCOMO)). We implemented a simplified version of COCOMO that computes the estimated person-year it took to develop the analyzed project. We use...

Thanks for the insights. I do not think verbosity is at fault here: it takes a reasonable amount of time to make an API call so the logs are printed...