You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All our nightly tests and builds operate on develop branch.
6
6
7
7
## Pull Request
8
-
> Note: If you already have a fork of Soot and need to merge our formatting changes, [this](https://github.com/Sable/soot/wiki/Merging-changes-after-introduction-of-formatting-guidelines) might help.
8
+
> Note: If you already have a fork of Soot and need to merge our formatting changes, [this](https://github.com/soot-oss/soot/wiki/Merging-changes-after-introduction-of-formatting-guidelines) might help.
9
9
10
10
To fix a problem in Soot or to contribute to Soot you can fork the Soot project on GitHub. This will generate a personal cloned repository for you to work on. To reincorporate your changes into Soot after they have been completed and tested, just send us a [pull request](https://help.github.com/articles/using-pull-requests). This will allow us to review your changes and merge them into the develop branch.
11
11
@@ -14,15 +14,15 @@ To fix a problem in Soot or to contribute to Soot you can fork the Soot project
14
14
Pull requests will have to conform to our coding style guidelines which are _as close as possible_* to the [Google Java Style Guide](https://google.github.io/styleguide/javaguide.html). Our build server will reject pull requests that do not comply with our guidelines.
15
15
16
16
Tutorials on how to apply automatic formatting and style enhancements can be found here:
Compliance with our guidelines is ensured by the Maven Checkstyle plugin. One can run the checks by invoking `mvn checkstyle:check`. Also, the check is bound to the Maven's `verify` phase.
21
21
Our build server will reject pull requests with existing violations.
22
22
23
23
### License header
24
24
25
-
Newly created classes will have to have a [correct license header](https://github.com/Sable/soot/wiki/License-Header) right after the _package declaration_ of the class. Our build server will reject pull requests with missing license headers. The license check can be run locally by invoking `mvn license:check-file-header` or during the `verify` phase.
25
+
Newly created classes will have to have a [correct license header](https://github.com/soot-oss/soot/wiki/License-Header) right after the _package declaration_ of the class. Our build server will reject pull requests with missing license headers. The license check can be run locally by invoking `mvn license:check-file-header` or during the `verify` phase.
26
26
27
27
**Make sure that `mvn clean verify` terminates successfully before setting up a pull request or committing to the repository directly!**
We are regularly applying for funding to help us maintain Soot. You can help us immensely by letting us know about [**projects that use Soot**](https://github.com/Sable/soot/wiki/Users-of-Soot), both commercially or in the form of research tools.
5
+
We are regularly applying for funding to help us maintain Soot. You can help us immensely by letting us know about [**projects that use Soot**](https://github.com/soot-oss/soot/wiki/Users-of-Soot), both commercially or in the form of research tools.
6
6
7
7
Also many thanks to [](https://www.ej-technologies.com/products/jprofiler/overview.html) for supporting Soot with a free-to-use open source license!
8
8
@@ -33,9 +33,9 @@ See http://www.sable.mcgill.ca/soot/ for details.
33
33
34
34
# How do I get started with Soot?
35
35
36
-
We have some documentation on Soot in the [wiki](https://github.com/Sable/soot/wiki) and also a large range of [tutorials](http://www.sable.mcgill.ca/soot/tutorial/index.html) on Soot.
36
+
We have some documentation on Soot in the [wiki](https://github.com/soot-oss/soot/wiki) and also a large range of [tutorials](http://www.sable.mcgill.ca/soot/tutorial/index.html) on Soot.
37
37
38
-
For detailed information please also consider the Soot's [JavaDoc and Options](https://github.com/Sable/soot/wiki/Options-and-JavaDoc) Documentations.
38
+
For detailed information please also consider the Soot's [JavaDoc and Options](https://github.com/soot-oss/soot/wiki/Options-and-JavaDoc) Documentations.
39
39
40
40
# Including Soot in your Project
41
41
@@ -66,7 +66,7 @@ The `soot-<RELEASE>.jar` file contains only Soot, allowing you to manually pick
66
66
67
67
# Building Soot yourself
68
68
69
-
If you cannot work with the prebuild versions and need to build Soot on your own, please consider the [wiki](https://github.com/Sable/soot/wiki/Building-Soot-from-the-Command-Line-(Recommended)) for further steps.
69
+
If you cannot work with the prebuild versions and need to build Soot on your own, please consider the [wiki](https://github.com/soot-oss/soot/wiki/Building-Soot-from-the-Command-Line-(Recommended)) for further steps.
70
70
71
71
# About Soot's source code
72
72
@@ -77,7 +77,7 @@ mailing list at: http://www.sable.mcgill.ca/mailman/listinfo/soot-list/
77
77
78
78
# How do I contribute to Soot?
79
79
80
-
We are happy to accept arbitrary improvements to Soot in form of GitHub pull requests. Please read our [contribution guidelines](https://github.com/Sable/soot/wiki/Contributing-to-Soot) before setting up a pull request.
80
+
We are happy to accept arbitrary improvements to Soot in form of GitHub pull requests. Please read our [contribution guidelines](https://github.com/soot-oss/soot/wiki/Contributing-to-Soot) before setting up a pull request.
81
81
82
82
# Please help us improve Soot!
83
83
You are using Soot and would like to help us support it in the future? Then please support us by filling out [this little web form](https://goo.gl/forms/rk1oSxFIxAH0xaf52).
0 commit comments