-
Notifications
You must be signed in to change notification settings - Fork 77
Adding a project to the Rascal libraries
Jurgen J. Vinju edited this page Sep 29, 2017
·
7 revisions
At https://update.rascal-mpl.org/libs/ we publish a set of Eclipse features which bundle Rascal projects that contain generic and reusable library feature or specific language support for programming languages.
To add a project to this update site, please follow the following steps:
- Create a Rascal project in Eclipse and add your Rascal and Java source code files.
- Make sure the project has a META-INF/RASCAL.MF file with the right information. If the project has a main function for example to register an Eclipse IDE language, this needs to be specified right there.
- Add a plugin.xml file with this extension:
<extension id="rascal-ecore-library" point="rascal_eclipse.rascalLibrary"> </extension>
- Copy a Jenkinsfile from an existing plugin, like
clair
- Copy a pom.xml from an existing plugin like
clair
and change the name of the project inside. -
git push
your project with the new pom.xml and Jenkinsfile - Go to http://ci.usethesource.io/ and edit the configuration of the SWAT organisation to include the new project name as one of the projects to search for a Jenkinsfile.
- Edit
rascal-eclipse-libraries/pom.xml
and add your new project as a module - Copy
-r
an existing feature project to a new project:cp -r rascal-eclipse-libraries/clair rascal-eclipse-libraries/my-project
- Edit `rascal-eclipse-libraries/my-project/feature.xml to contain the right information
git commit -am "added new feature"; git push
- Done.
If your project contains Java code then it is imperative to have configured build.properties
in such a way that:
- All Rascal source files en up in the jar in a sub-folder called
src
- All class files end up in the top-level jar
Example build.properties file:
bin.includes = META-INF/,\
src/,\
plugin.xml,\
LICENSE,\
CITATION,\
.
source.. = src/