COPPER - the high performance Java workflow engine.
COPPER is an open-source, powerful, light-weight, and easily configurable workflow engine. The power of COPPER is that it uses Java as a description language for workflows. The project artifacts can be found on Maven Central. See copper-engine.org for more information.
How to build
COPPER is built using Gradle. However, you don't need to install Gradle, because COPPER is using the Gradle wrapper. Note: If you are behind an internet proxy, you have to configure the corresponding system properties in gradle. See Accessing the web via a proxy.
To build all COPPER projects, just execute the following in the projects root directory:
If you want to build all and run all tests, just execute:
To generate Eclipse project files, run:
once in the projects root directory and open the corresponding projects with the eclipse IDE. (You must perform this step every time the project dependencies change).
How to contribute
- Create an issue on GitHub.
- Create a fork on GitHub.
- Configure your IDE (Eclipse, IntelliJ IDEA) as described below.
./gradlew assembleonce if you haven't done so in step 3. This will generate some WSDL stubs needed for some tests.
- Commit your changes incl. WHATSNEW.txt
- Ensure, that your sources are UTF-8 encoded!
- Ensure, that your sources start with our Apache License header. (The build will fail if they don't.)
- Build all and run tests: ./gradlew clean build
- Push your changes to your fork.
- Create a pull request on GtHub.
How to configure your IDE
./gradlew eclipse once. This will create Eclipse project files which you can import. This also creates proper code style settings. Before committing you should always reformat the code. You can configure Eclipse to do this automatically on each save.
Every time a dependency changes in
build.gradle you must run
./gradlew eclipse again. You don't need to restart Eclipse for this, simply press F5 on the projects.
Before you open the project in IntelliJ for the first time, run
./gradlew assemble once. This also creates proper code style settings, which IntelliJ automatically picks up. After that open
build.gradle with "File->Open" and follow the instructions, accept the defaults.
Before committing you should always reformat the code. You can configure IntelliJ to do this automatically on each commit.
Copyright 2002-2018 Copper Engine Development Team
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.