Files
SCM-Manager/docs/en/build-from-source.md

41 lines
1.3 KiB
Markdown
Raw Normal View History

2020-03-31 17:28:30 +02:00
# Building SCM-Manager from source
2020-03-09 08:01:43 +01:00
### Software Requirements
2020-03-31 17:28:30 +02:00
- JDK 1.7 or higher
([download](http://www.oracle.com/technetwork/java/index.html))
- Maven 3 or higher ([download](http://maven.apache.org/))
- Mercurial ([download](https://www.mercurial-scm.org/))
2020-03-09 08:01:43 +01:00
### Build SCM-Manager 1.x from source
2020-03-31 17:28:30 +02:00
```bash
hg clone https://bitbucket.org/sdorra/scm-manager
cd scm-manager
hg update 1.x
mvn clean install
```
**Note**: if you use the \"package\" phase rather than the \"install\" phase,
the standalone version may include an old version of the WAR file in the distribution bundle,
rather than the version you just built.
2020-03-09 08:01:43 +01:00
After mvn finished, the war bundle is located at
2020-03-31 17:28:30 +02:00
**scm-webapp/target/scm-webapp.war** and the standalone version is
located at **scm-server/target/scm-server-app**.
2020-03-09 08:01:43 +01:00
2020-03-31 17:28:30 +02:00
You can also start a dev server using `mvn jetty:run-war -f
scm-webapp`. SCM-Manager is served at <http://localhost:8081/scm>.
2020-03-09 08:01:43 +01:00
### REST
Docs:
2020-03-31 17:28:30 +02:00
- Create the documentation: `mvn -f scm-webapp compile -P doc`
- The documentation can be found at scm-webapp/target/restdocs
2020-03-09 08:01:43 +01:00
Note that if using jetty (see above) you have to access
<http://localhost:8081/scm> once, to trigger creation of the
2020-03-31 17:28:30 +02:00
`scmadmin` user. Then you can access the REST api directly
2020-03-09 08:01:43 +01:00
<http://localhost:8081/scm/api/rest>