Enable creators of repositories to choose a template repository upon initialization
Enable creators of repositories to choose a template repository upon initialization. Repositories with a specific configuration file are marked as templates and will be automatically detected by SCM-Manager.
The plugin can be compiled and packaged with the normal maven lifecycle:
- clean -
mvn clean- removes the target directory, can be combined with other phases
- compile -
mvn compile- compiles Java code and creates the ui bundle
- test -
- install -
mvn install- installs the plugin (smp and jar) in the local maven repository
- package -
mvn package- creates the final plugin bundle (smp package) in the target folder
- deploy -
mvn deploy- deploys the plugin (smp and jar) to the configured remote repository
For the development and testing the
serve lifecycle of the plugin can be used:
- run -
mvn run- starts scm-manager with the plugin pre installed.
If the plugin was started with
mvn run, the default browser of the os should be automatically opened.
If the browser does not start automatically, start it manually and go to http://localhost:8081/scm.
In this mode each change to web files (src/main/js or src/main/webapp), should trigger a reload of the browser with the made changes. If you compile a class (e.g.: with your IDE from src/main/java to target/classes), the SCM-Manager context will restart automatically. So you can see your changes without restarting the server.
A quick look at the files and directories you'll see in a SCM-Manager project.
. ├── node_modules/ ├── src/ | ├── main/ | | ├── java/ | | ├── js/ | | └── resources/ | ├── test/ | | ├── java/ | | └── resources/ | └── target/ ├── .editorconfig ├── .gitignore ├── CHANGELOG.md ├── LICENSE ├── package.json ├── pom.xml ├── README.md ├── tsconfig.json └── yarn.lock
node_modules/: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
src/: This directory will contain all of the code related to what you see or not.
srcis a convention for “source code”.
java/: This directory contain the Java code.
resources/: This directory contains the the classpath resources.
java/: This directory contains the Java unit tests.
resources/: This directory contains classpath resources for unit tests.
target/: This is the build directory.
.editorconfig: This is a configuration file for your editor using EditorConfig. The file specifies a style that IDEs use for code.
.gitignore: This file tells git which files it should not track / not maintain a version history for.
CHANGELOG.md: All notable changes to this project will be documented in this file.
LICENSE: This project is licensed under the MIT license.
package.json: Here you can find the dependency/build configuration and dependencies for the frontend.
pom.xml: Maven configuration, which also includes things like metadata.
README.md: This file, containing useful reference information about the project.
tsconfig.jsonThis is the typescript configuration file.
yarn.lock: This is the ui dependency configuration.
- Community Support - Contact the SCM-Manager support team for questions about SCM-Manager, to report bugs or to request features through the official channels. Find more about this here.
- Enterprise Support - Do you require support with the integration of SCM-Manager into your processes, with the customization of the tool or simply a service level agreement (SLA)? Contact our development partner Cloudogu! Their team is looking forward to discussing your individual requirements with you and will be more than happy to give you a quote. Request Enterprise Support.