-
Notifications
You must be signed in to change notification settings - Fork 78
Rascal Developers Setup Step by Step
Some general git tips, and a few github specific tips.
-
be sure to setup your name in git:
git config --global user.name "Rascal Developer #42"
-
be sure to setup your email address:
git config --global user.email "[email protected]"
(this should match one of the email addresses in your profile) -
use the ssh URLs, they are easier to use, especially in combination with public keys.
-
make sure you use the ssh over port
443
tunneling trick this will assure you are able to access the repository anywhere :). -
Run this command
git config --global pull.rebase preserve
to avoid merge-commits but instead let pull rebase your unpushed commites on top of the remote commits- If conflict arises, you have to fix them as before, however, you have to remember to type
git rebase --continue
instead ofgit commit
- If you would want to merge a branch, make sure not to use
pull
, but usefetch
&&merge --no-ff
.
- If conflict arises, you have to fix them as before, however, you have to remember to type
Binary builds (of development snapshots and released versions) of usethesource artifacts are available from our own repository. This implies that if you are interested in contribution to a single usethesource project, it should mostly suffice to check solely that specific source repository. All other dependencies are provided as binary artifacts.
The locations of our binary artifact repository is pre-configured in the build configurations of current usethesource projects. There's nothing more to do. For reference we exemplify how to add usethesource dependencies to other projects. In case you use Maven for dependency management, you have to add another repository location to your pom.xml file:
<repositories>
<repository>
<id>usethesource</id>
<url>http://nexus.rascal-mpl.org/repository/maven-public/</url>
</repository>
</repositories>
Furthermore, you have to declare the project an version as a dependency. In this example we use capsule version 0.2.0 as an example. To reference this specific version, insert the following snippet in your pom.xml file:
<dependency>
<groupId>io.usethesource</groupId>
<artifactId>capsule</artifactId>
<version>0.2.0</version>
</dependency>
Snippets for other build tools and dependency management systems may vary slightly.
The following projects should all reside in the same workspace which you use to develop Rascal:
- Import the above projects as existing projects into Eclipse, and you are all set to:
- Run a second level Eclipse
- Or
Run as
the RascalShell from the rascal-shell project
- In the order given above, type
mvn clean install
in every cloned project
Afterwards there are still some dependencies that have to be installed as Eclipse plug-ins: