usethesource/rascal-maven-plugin issues and pull requests

#24 - Fixed code generation phase for multi-module maven projects

Pull Request - State: closed - Opened by rodinaarssen 4 months ago

#23 - replacing lib scheme

Pull Request - State: open - Opened by jurgenvinju 4 months ago

#22 - use tutor code from rascal project, drop dependency on rascal-tutor prokect and inject screenshotter into the tutor repl command executor

Pull Request - State: open - Opened by jurgenvinju 7 months ago - 1 comment

#21 - `[WARNING] Monitor of Rascal compiler is over max (17) by 1`

Issue - State: open - Opened by DavyLandman 8 months ago

#20 - Fixed bug that would hide the failure of the nested jvm

Pull Request - State: closed - Opened by DavyLandman 10 months ago - 1 comment

#19 - make use of the new progress bar monitor in interactive mode, while remaining with the logger MojoRascalMonitor in batch mode

Pull Request - State: closed - Opened by jurgenvinju 10 months ago

#18 - Incremental Rascal builder does not report older errors again (of the non-stale files)

Issue - State: open - Opened by jurgenvinju 10 months ago

#18 - Incremental Rascal builder does not report older errors again (of the non-stale files)

Issue - State: open - Opened by jurgenvinju 10 months ago

#17 - Errors reported with the wrong module names using rascal-core 0.8.7-BOOT1

Issue - State: closed - Opened by jurgenvinju 11 months ago - 5 comments

#16 - Stale source file computation is broken for the Rascal checker (RascalCompilerMojo)

Issue - State: closed - Opened by jurgenvinju 11 months ago - 1 comment

#15 - for non-package courses the bin folder now becomes the root of the generated site

Pull Request - State: open - Opened by jurgenvinju over 1 year ago

#14 - |lib://rascal-tutor|.ls produces contents of `|lib://rascal|` instead while running the tutor

Issue - State: closed - Opened by jurgenvinju over 1 year ago - 1 comment

#13 - Rascal-core failes and mentions not finding `std:///List.rsc`

Issue - State: open - Opened by DavyLandman about 2 years ago - 19 comments
Labels: bug

#12 - add tutor package feature

Pull Request - State: closed - Opened by jurgenvinju about 2 years ago

#11 - weird that we don't have a `mvn rascal:test` or simply `mvn test` plugin to run the Rascal tests in a project.

Issue - State: open - Opened by jurgenvinju about 2 years ago

#10 - Run actions on windows & osx as well

Issue - State: closed - Opened by DavyLandman over 2 years ago
Labels: enhancement

#9 - Add tutor to the test suite run in the github actions.

Issue - State: open - Opened by DavyLandman over 2 years ago
Labels: enhancement

#8 - Tutor compiler crashes (on Windows?)

Issue - State: open - Opened by DavyLandman over 2 years ago - 5 comments
Labels: bug

#7 - Command-line console is broken for the Rascal project

Issue - State: closed - Opened by rodinaarssen about 3 years ago

#6 - Command-line console is broken on Windows

Issue - State: closed - Opened by rodinaarssen about 3 years ago

#5 - too many stale files detected on running the compiler again

Issue - State: open - Opened by jurgenvinju about 3 years ago
Labels: bug

#4 - java11 branch with dependency on 0.6.x of typepal and rascal-core does not work

Issue - State: closed - Opened by jurgenvinju about 3 years ago - 1 comment

#3 - Omission of `<sourceLookup>` attribute from `pom.xml` yields a stack overflow in the type checker

Issue - State: closed - Opened by rodinaarssen over 3 years ago - 1 comment

#2 - Bump junit from 4.8.2 to 4.13.1

Pull Request - State: closed - Opened by dependabot[bot] over 4 years ago
Labels: dependencies

#1 - allow and force source directories to have the |project://<projectName>| scheme

Issue - State: open - Opened by jurgenvinju about 5 years ago

Ecosyste.ms: Issues

GitHub / usethesource/rascal-maven-plugin issues and pull requests

#24 - Fixed code generation phase for multi-module maven projects

#23 - replacing lib scheme

#22 - use tutor code from rascal project, drop dependency on rascal-tutor prokect and inject screenshotter into the tutor repl command executor

#21 - `[WARNING] Monitor of Rascal compiler is over max (17) by 1`

#20 - Fixed bug that would hide the failure of the nested jvm

#19 - make use of the new progress bar monitor in interactive mode, while remaining with the logger MojoRascalMonitor in batch mode

#18 - Incremental Rascal builder does not report older errors again (of the non-stale files)

#18 - Incremental Rascal builder does not report older errors again (of the non-stale files)

#17 - Errors reported with the wrong module names using rascal-core 0.8.7-BOOT1

#16 - Stale source file computation is broken for the Rascal checker (RascalCompilerMojo)

#15 - for non-package courses the bin folder now becomes the root of the generated site

#14 - |lib://rascal-tutor|.ls produces contents of `|lib://rascal|` instead while running the tutor

#13 - Rascal-core failes and mentions not finding `std:///List.rsc`

#12 - add tutor package feature

#11 - weird that we don't have a `mvn rascal:test` or simply `mvn test` plugin to run the Rascal tests in a project.

#10 - Run actions on windows & osx as well

#9 - Add tutor to the test suite run in the github actions.

#8 - Tutor compiler crashes (on Windows?)

#7 - Command-line console is broken for the Rascal project

#6 - Command-line console is broken on Windows

#5 - too many stale files detected on running the compiler again

#4 - java11 branch with dependency on 0.6.x of typepal and rascal-core does not work

#3 - Omission of `<sourceLookup>` attribute from `pom.xml` yields a stack overflow in the type checker

#2 - Bump junit from 4.8.2 to 4.13.1

#1 - allow and force source directories to have the |project://<projectName>| scheme