-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation building process #1907
Comments
Should explain that meta inf is used (besides others) to identify rascal project when resolving dependencies (rather than pom file, still no idea if that is used for anything outside of maven) |
One of the reasons is that we do not really like RASCAL.MF, and want to replace it with something better. Both the semantics and the syntax. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, the role of the RASCAL.MF and the pom.xml file in a Rascal project are not well documented.
What I found was the comment for lib schemes.
It would be nice to have a description what is needed in order to get a Rascal project to successfully build using Maven that includes the role of the individual files in the context of Rascal. The documentation can reference the Maven manual for not Rascal specific things
The text was updated successfully, but these errors were encountered: