| commit | 45d2cc88c42309d4745953f08ecab03b0e5ce118 | [log] [tgz] |
|---|---|---|
| author | Christofer Dutz <christofer.dutz@c-ware.de> | Mon Sep 17 18:31:32 2018 +0200 |
| committer | Christofer Dutz <christofer.dutz@c-ware.de> | Mon Sep 17 18:31:32 2018 +0200 |
| tree | ade1a7a983f339b1f0727e412d8eb47fd68f9e44 | |
| parent | c3506966f7dc95dd86b2b1be72c1da58f618edfe [diff] |
[maven-release-plugin] prepare release plc4x-parent-0.1.0
Apache PLC4X is an effort to create a set of libraries for communicating with industrial grade programmable logic controllers (PLCs) in a uniform way. We are planning on shipping libraries for usage in:
As well as provide direct integration into other Apache projects, such as:
Currently the project is configured to require the following software:
As currently a lot of the work is being done in the documentation and this is handled by mavens site plugin, in order to get all parts built, it is important to also trigger Mavens site generation. This is done by adding the site:site goal to the execution.
Unix/Linux/Mac:
./mvnw clean install site:site
Windows:
mvnw.cmd clean install site:site
This will generate all artifacts as well as their documentation. In order to locally fully test the generated documentation site, it is advisable to add another goal site:stage to the build, which will copy the sub-sites of all modules into one directory target/staging. Without this the links between modules will not work correctly.
Unix/Linux/Mac:
./mvnw clean install site:site site:stage
Windows:
mvnw.cmd clean install site:site site:stage