Vincent Blondeau

Todo: Comment of @girba: I would want a different design for the options that does not involve so many ifs. That needs to be reworked.

Snippet of code to reproduce (need Junit lib for annotation): ``` import java.io.IOException; import org.junit.Test; public class Temp { @Test public void test1() throws IOException { } } ``` By...

E.g: ``` public class GlobalControllerExceptionHandler { @ResponseStatus(HttpStatus.BAD_REQUEST) public String handleException(final Exception ex) { return ex.getMessage(); } ``` `HttpStatus`do not contains the enum value `BAD_REQUEST`

For example: ``` public class GlobalControllerExceptionHandler { @ResponseBody @ResponseStatus(HttpStatus.BAD_REQUEST) @ExceptionHandler({ NotSupportedCountryException.class, WrongPeriodException.class }) public String handleException(final Exception ex) { return ex.getMessage(); } } ``` references to `HttpStatus`, `NotSupportedCountryException`and `WrongPeriodException`are not...

Add the list of Jar needed for the parsing as cmd arg

8

Because on maven projects, the jars are not in the source code dir and there is a huge amount of data that you don't want to copy...

Proper Handling of the Undo Stack in the RBRefactoryChangeManager

6

RBRefactoryChangeManager uses a Stack to handle the undo collection. The stack top is the first element but it is not correctly managed. This could partially fix https://github.com/pharo-project/pharo/issues/8103