Closed leegbestand closed 2 years ago
True, we should think about better feedback.
Workaround:
It needs a pom.xml
file. .project
is not used.
In util::Reflective
there is an a function that setups a project correctly: https://github.com/usethesource/rascal/blob/bec47a0fd41662c48d4851f80d92c32595094d9c/src/org/rascalmpl/library/util/Reflective.rsc#L315
Dear @DavyLandman ,
Thank you for the response. I tried to setup a new project using newRascalProject
, but I still get the same behaviour.
It seems that the RASCAL.MF file is missing the Manifest-Version
entry. When I add this entry with a value, the error is gone.
So, updating the RASCAL.MF to the following:
Manifest-Version: 0.0.1
Project-Name: se
Source: src/main/rascal
Require-Libraries:
works for me. I am not sure if the version has any effect? I tried several version and it seemed to have no effect.
ok. so when there is a MANIFEST.MF present in the same folder with a Manifest-Version:
then everything works fine, but if the RASCAL.MF
is alone, then it needs a Manifest-Version
. weirdness
I've added Manifest-Version
to the template. Considering this fixed for now, because letting the code work on broken RASCAL.MF files would require a lot of code.
LS,
Describe the bug
The VScode plugin does not work when the current project has no or an incorrect RASCAL.MF or .project file. Instead, it gives an internal error in the output console and a Request textDocument/documentSymbol error popup in the bottom right corner.
To Reproduce
Steps to reproduce the behavior:
Expected behavior I would expect it to work or a helpful error message indicating the requirement for the RASCAL.MF and .project file.
Stack traces
Desktop (please complete the following information):
** Additional context The minimal viable directory structure that seems to be working for me is the following: