Google Git
Sign in
apache / plc4x / refs/tags/Last-Mina-Version
tag7b1ac89a26ece3e38a5c48b1d969a04593327a44
taggerChristofer Dutz <christofer.dutz@codecentric.de>Thu Nov 30 15:27:44 2017 +0000
object047ef633fc03d0c2cd1b7985830292dbbb039afd 
commit047ef633fc03d0c2cd1b7985830292dbbb039afd[log] [tgz]
authorChristofer Dutz <christofer.dutz@c-ware.de>Fri Nov 24 11:44:41 2017 +0100
committerChristofer Dutz <christofer.dutz@c-ware.de>Fri Nov 24 11:44:41 2017 +0100
tree5506980f8f859e8a294c4df6dbb433b7401dd1ab
parente73f92206a8f774143c60624811444f647763ca6 [diff]
- Changed the PlcLogger to the changes in the PlcConnection api.

1 file changed
tree: 5506980f8f859e8a294c4df6dbb433b7401dd1ab
  1. .mvn/
  2. applications/
  3. integrations/
  4. plc4c/
  5. plc4j/
  6. plc4s/
  7. src/
  8. .editorconfig
  9. .gitignore
  10. .gitlab-ci.yml
  11. .travis.yml
  12. DEVELOPMENT.md
  13. Jenkinsfile
  14. mvnw
  15. mvnw.cmd
  16. pom.xml
  17. README.md
README.md
Welcome to Apache PLC4X!
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:
  1. Java
  2. Scala
  3. C/C++
As well as provide direct integration into other Apache projects, such as:
  1. Apache Edgent
  2. Apache Mynewt
Environment
Currently the project is configured to require the following software:
  1. Java 8 JDK: For running Maven in general as well as compiling the Java and Scala modules `JAVA_HOME configured to point to that.
  2. (Optional) Graphwiz: For generating the graphs in the documentation (http://www.graphviz.org/)
Getting Started
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