You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@plc4x.apache.org by Christofer Dutz <ch...@c-ware.de> on 2019/04/29 12:37:53 UTC
Major update to the build just merged to develop
Hi all,
I just wanted to inform you that I just merged the feature/PLC4X-111-interop-server branch back to develop.
I greatly refactored the way the build works so it should be a lot simpler and produce less problems, especially for the platform-dependent c++ stuff.
Also did I update the main README with all the prerequisites on the different platforms (Tested with Mac, Linux (Ubuntu 18.04), Windows 10).
I guess over the weekend I probably did 20-30 full builds on every of the 3 platforms with multiple different JDK versions … also did I setup clean VMs (fleshly installed systems) for all of the environments, so I hopefully got all the prerequisites needed.
It would be super-great if you guys could give the build a spin on your systems:
mvnw clean install site -P with-cpp,with-python,with-proxies,with-sandbox
The above command should build EVERYTHING … probably a good idea to start this when starting the next Game Of Thrones episode that came out last night ;-)
Feedback greatly appreciated.
Now I’ll create a new feature branch and try to untangle the examples, integrations and sandbox modules so we have something to discuss.
Chris
Re: Major update to the build just merged to develop
Posted by Christofer Dutz <ch...@c-ware.de>.
From the jenkins build I have this:
-- Building without tests
-- Found FLEX: /usr/bin/flex (found version "2.6.0")
-- Found BISON: /usr/bin/bison (found version "3.0.4")
-- ----------------------------------------------------------
-- Thrift version: 0.12.0 (0.2.0)
-- Thrift package version: 0.12.0
-- Build configuration Summary
-- Build Thrift compiler: ON
-- Build compiler plugin support: OFF
-- Build with unit tests: OFF
-- Build examples: ON
-- Build Thrift libraries: ON
-- Language libraries:
-- Build C++ library: OFF
-- - Boost headers missing
-- C++ Language Level: C++11 [fallback to earlier if compiler does not support it]
-- Build C (GLib) library: OFF
-- - GLib missing
-- Build Java library: OFF
-- Build Python library: ON
-- Build Haskell library: OFF
-- - GHC missing
-- - Cabal missing
-- Library features:
-- Build shared libraries: ON
-- Build static libraries: ON
-- Build with Boost static link library: OFF
-- Build with Boost thread support: OFF
-- Build with boost/tr1/functional (forced) OFF
-- Build with boost/smart_ptr (forced) OFF
-- Build with C++ std::thread support: OFF
-- Build with libevent support: OFF
-- Build with OpenSSL support: OFF
-- Build with Qt4 support: OFF
-- Build with Qt5 support: OFF
-- Build with ZLIB support: OFF
You can see the:
-- Build Python library: ON
If this is OFF, you will get the problem you reported.
Chris
Am 29.04.19, 15:43 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Ok ... as it's executing package-thrift-python you have enabled the "with-python" config.
The problem here is, that probably the build isn't finding the python executable. Therefore the build is simply disabling the python generation.
The problem is that we're trying to package the out put ... could you please have a look at the cmake-generate part if it compains or simply outputs that it's not building the python libs. Also please check the output of running "python --version" on the commandline.
Chris
Am 29.04.19, 15:13 schrieb "Julian Feinauer" <j....@pragmaticminds.de>:
Hi chris,
form e there is an exception in the build with the following (truncated) output:
[INFO] --- maven-assembly-plugin:3.1.1:single (package-thrift-python) @ plc4x-tools-thrift ---
[INFO] Reading assembly descriptor: src/assembly/python.xml
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for PLC4X 0.4.0-SNAPSHOT:
[INFO]
[INFO] PLC4X .............................................. SUCCESS [ 38.489 s]
[INFO] Protocols .......................................... SUCCESS [ 3.410 s]
[INFO] Protocols: Test-Utils .............................. SUCCESS [ 11.189 s]
[INFO] Protocols: KNXNet-IP ............................... SUCCESS [ 24.445 s]
[INFO] Protocols: S7 ...................................... SUCCESS [ 43.319 s]
[INFO] Protocols: Proxy ................................... SUCCESS [ 4.481 s]
[INFO] PLC4J .............................................. SUCCESS [ 2.941 s]
[INFO] PLC4J: Utils ....................................... SUCCESS [ 2.219 s]
[INFO] PLC4J: Utils: Test Utils ........................... SUCCESS [ 5.051 s]
[INFO] PLC4J: API ......................................... SUCCESS [ 9.116 s]
[INFO] PLC4J: Protocols ................................... SUCCESS [ 3.506 s]
[INFO] PLC4J: Protocols: Driver-Bases ..................... SUCCESS [ 2.042 s]
[INFO] PLC4J: Protocol: Driver-Base: Base ................. SUCCESS [ 23.471 s]
[INFO] PLC4J: Protocol: Driver-Base: Test ................. SUCCESS [ 7.968 s]
[INFO] PLC4J: Protocol: ADS ............................... SUCCESS [ 17.576 s]
[INFO] PLC4J: Protocol: Driver-Base: TCP .................. SUCCESS [ 4.352 s]
[INFO] PLC4J: Protocol: Driver-Base: Serial ............... SUCCESS [ 4.525 s]
[INFO] PLC4J: Drivers ..................................... SUCCESS [ 2.148 s]
[INFO] PLC4J: Driver: ADS ................................. SUCCESS [ 25.162 s]
[INFO] PLC4J: Protocol: Ethernet/IP ....................... SUCCESS [ 4.300 s]
[INFO] PLC4J: Driver: Ethernet/IP ......................... SUCCESS [ 6.496 s]
[INFO] PLC4J: Protocol: Modbus ............................ SUCCESS [ 6.726 s]
[INFO] PLC4J: Driver: Modbus .............................. SUCCESS [ 23.552 s]
[INFO] PLC4J: Protocol: ISO on TCP ........................ SUCCESS [ 7.007 s]
[INFO] PLC4J: Protocol: ISO TP ............................ SUCCESS [ 7.962 s]
[INFO] PLC4J: Protocol: S7 ................................ SUCCESS [ 14.038 s]
[INFO] PLC4J: Driver: S7 .................................. SUCCESS [ 9.578 s]
[INFO] PLC4J: Driver: Simulated ........................... SUCCESS [ 17.948 s]
[INFO] PLC4J: Protocol: Driver-Base: Raw Socket ........... SUCCESS [ 4.128 s]
[INFO] PLC4J: Protocol: Delta-V ........................... SUCCESS [ 7.550 s]
[INFO] PLC4J: Protocol: Benchmarks ........................ SUCCESS [ 5.732 s]
[INFO] PLC4J: Utils: Connection Pool ...................... SUCCESS [ 6.509 s]
[INFO] PLC4J: Utils: Object PLC Mapping ................... SUCCESS [ 11.039 s]
[INFO] PLC4J: Utils: Raw-Sockets .......................... SUCCESS [ 6.195 s]
[INFO] PLC4J: Utils: Scraper .............................. SUCCESS [ 10.349 s]
[INFO] Tools .............................................. SUCCESS [ 2.098 s]
[INFO] Tools: Thrift ...................................... FAILURE [02:11 min]
[INFO] PLC4J: Utils: Interop-Server ....................... SKIPPED
[INFO] PLC4PY ............................................. SKIPPED
[INFO] Integrations ....................................... SKIPPED
[INFO] Integrations: Apache Brooklyn ...................... SKIPPED
[INFO] Integrations: Apache Camel ......................... SKIPPED
[INFO] Integrations: Apache Edgent ........................ SKIPPED
[INFO] Integrations: Apache Kafka ......................... SKIPPED
[INFO] Integrations: Apache Mynewt ........................ SKIPPED
[INFO] Integrations: Apache Nifi .......................... SKIPPED
[INFO] Integrations: Apache Nifi: Processors .............. SKIPPED
[INFO] Integrations: Apache Nifi: NAR ..................... SKIPPED
[INFO] Integrations: Apache Karaf ......................... SKIPPED
[INFO] Integrations: Apache Karaf: ADS .................... SKIPPED
[INFO] Integrations: Apache Karaf: EtherNet/IP ............ SKIPPED
[INFO] Integrations: Apache Karaf: Modbus ................. SKIPPED
[INFO] Integrations: Apache Karaf: S7 ..................... SKIPPED
[INFO] Integrations: Apache Karaf: Simulated .............. SKIPPED
[INFO] Integrations: Apache Karaf: Demo Server ............ SKIPPED
[INFO] Integrations: Apache Calcite ....................... SKIPPED
[INFO] Examples ........................................... SKIPPED
[INFO] Examples: Protocol: Dummy .......................... SKIPPED
[INFO] Examples: Cloud: Azure IoT Hub ..................... SKIPPED
[INFO] Examples: Cloud: Google Cloud IoT Core ............. SKIPPED
[INFO] Examples: Connectivity: Kafka ...................... SKIPPED
[INFO] Examples: Connectivity: MQTT ....................... SKIPPED
[INFO] Examples: Edgent ................................... SKIPPED
[INFO] Examples: Hello OPM ................................ SKIPPED
[INFO] Examples: Storage: ElasticSearch ................... SKIPPED
[INFO] Examples: Hello-Webapp (root) ...................... SKIPPED
[INFO] Examples: Hello-Webapp: Client ..................... SKIPPED
[INFO] Examples: Hello-Webapp: Service .................... SKIPPED
[INFO] Examples: Hello-Webapp: Spring-Boot WAR ............ SKIPPED
[INFO] Examples: Hello-World PLC4X ........................ SKIPPED
[INFO] PLC4Cpp ............................................ SKIPPED
[INFO] PLC4Cpp: Libs ...................................... SKIPPED
[INFO] PLC4Cpp: Libs: Boost ............................... SKIPPED
[INFO] PLC4Cpp: API ....................................... SKIPPED
[INFO] PLC4Cpp: Protocols ................................. SKIPPED
[INFO] PLC4Cpp: Protocols: Driver-Bases ................... SKIPPED
[INFO] PLC4Cpp: Protocols: Driver-Base: Base .............. SKIPPED
[INFO] PLC4Cpp: Utils ..................................... SKIPPED
[INFO] Sandbox ............................................ SKIPPED
[INFO] Sandbox: Dynamic-Driver: (Base) .................... SKIPPED
[INFO] Sandbox: Dynamic-Driver: S7 ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:41 min
[INFO] Finished at: 2019-04-29T15:00:31+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.1:single (package-thrift-python) on project plc4x-tools-thrift: Failed to create assembly: Error creating assembly archive python: archive cannot be empty -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :plc4x-tools-thrift
Hope that helps
Julian
Am 29.04.19, 14:38 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
I just wanted to inform you that I just merged the feature/PLC4X-111-interop-server branch back to develop.
I greatly refactored the way the build works so it should be a lot simpler and produce less problems, especially for the platform-dependent c++ stuff.
Also did I update the main README with all the prerequisites on the different platforms (Tested with Mac, Linux (Ubuntu 18.04), Windows 10).
I guess over the weekend I probably did 20-30 full builds on every of the 3 platforms with multiple different JDK versions … also did I setup clean VMs (fleshly installed systems) for all of the environments, so I hopefully got all the prerequisites needed.
It would be super-great if you guys could give the build a spin on your systems:
mvnw clean install site -P with-cpp,with-python,with-proxies,with-sandbox
The above command should build EVERYTHING … probably a good idea to start this when starting the next Game Of Thrones episode that came out last night ;-)
Feedback greatly appreciated.
Now I’ll create a new feature branch and try to untangle the examples, integrations and sandbox modules so we have something to discuss.
Chris
Re: Major update to the build just merged to develop
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... as it's executing package-thrift-python you have enabled the "with-python" config.
The problem here is, that probably the build isn't finding the python executable. Therefore the build is simply disabling the python generation.
The problem is that we're trying to package the out put ... could you please have a look at the cmake-generate part if it compains or simply outputs that it's not building the python libs. Also please check the output of running "python --version" on the commandline.
Chris
Am 29.04.19, 15:13 schrieb "Julian Feinauer" <j....@pragmaticminds.de>:
Hi chris,
form e there is an exception in the build with the following (truncated) output:
[INFO] --- maven-assembly-plugin:3.1.1:single (package-thrift-python) @ plc4x-tools-thrift ---
[INFO] Reading assembly descriptor: src/assembly/python.xml
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for PLC4X 0.4.0-SNAPSHOT:
[INFO]
[INFO] PLC4X .............................................. SUCCESS [ 38.489 s]
[INFO] Protocols .......................................... SUCCESS [ 3.410 s]
[INFO] Protocols: Test-Utils .............................. SUCCESS [ 11.189 s]
[INFO] Protocols: KNXNet-IP ............................... SUCCESS [ 24.445 s]
[INFO] Protocols: S7 ...................................... SUCCESS [ 43.319 s]
[INFO] Protocols: Proxy ................................... SUCCESS [ 4.481 s]
[INFO] PLC4J .............................................. SUCCESS [ 2.941 s]
[INFO] PLC4J: Utils ....................................... SUCCESS [ 2.219 s]
[INFO] PLC4J: Utils: Test Utils ........................... SUCCESS [ 5.051 s]
[INFO] PLC4J: API ......................................... SUCCESS [ 9.116 s]
[INFO] PLC4J: Protocols ................................... SUCCESS [ 3.506 s]
[INFO] PLC4J: Protocols: Driver-Bases ..................... SUCCESS [ 2.042 s]
[INFO] PLC4J: Protocol: Driver-Base: Base ................. SUCCESS [ 23.471 s]
[INFO] PLC4J: Protocol: Driver-Base: Test ................. SUCCESS [ 7.968 s]
[INFO] PLC4J: Protocol: ADS ............................... SUCCESS [ 17.576 s]
[INFO] PLC4J: Protocol: Driver-Base: TCP .................. SUCCESS [ 4.352 s]
[INFO] PLC4J: Protocol: Driver-Base: Serial ............... SUCCESS [ 4.525 s]
[INFO] PLC4J: Drivers ..................................... SUCCESS [ 2.148 s]
[INFO] PLC4J: Driver: ADS ................................. SUCCESS [ 25.162 s]
[INFO] PLC4J: Protocol: Ethernet/IP ....................... SUCCESS [ 4.300 s]
[INFO] PLC4J: Driver: Ethernet/IP ......................... SUCCESS [ 6.496 s]
[INFO] PLC4J: Protocol: Modbus ............................ SUCCESS [ 6.726 s]
[INFO] PLC4J: Driver: Modbus .............................. SUCCESS [ 23.552 s]
[INFO] PLC4J: Protocol: ISO on TCP ........................ SUCCESS [ 7.007 s]
[INFO] PLC4J: Protocol: ISO TP ............................ SUCCESS [ 7.962 s]
[INFO] PLC4J: Protocol: S7 ................................ SUCCESS [ 14.038 s]
[INFO] PLC4J: Driver: S7 .................................. SUCCESS [ 9.578 s]
[INFO] PLC4J: Driver: Simulated ........................... SUCCESS [ 17.948 s]
[INFO] PLC4J: Protocol: Driver-Base: Raw Socket ........... SUCCESS [ 4.128 s]
[INFO] PLC4J: Protocol: Delta-V ........................... SUCCESS [ 7.550 s]
[INFO] PLC4J: Protocol: Benchmarks ........................ SUCCESS [ 5.732 s]
[INFO] PLC4J: Utils: Connection Pool ...................... SUCCESS [ 6.509 s]
[INFO] PLC4J: Utils: Object PLC Mapping ................... SUCCESS [ 11.039 s]
[INFO] PLC4J: Utils: Raw-Sockets .......................... SUCCESS [ 6.195 s]
[INFO] PLC4J: Utils: Scraper .............................. SUCCESS [ 10.349 s]
[INFO] Tools .............................................. SUCCESS [ 2.098 s]
[INFO] Tools: Thrift ...................................... FAILURE [02:11 min]
[INFO] PLC4J: Utils: Interop-Server ....................... SKIPPED
[INFO] PLC4PY ............................................. SKIPPED
[INFO] Integrations ....................................... SKIPPED
[INFO] Integrations: Apache Brooklyn ...................... SKIPPED
[INFO] Integrations: Apache Camel ......................... SKIPPED
[INFO] Integrations: Apache Edgent ........................ SKIPPED
[INFO] Integrations: Apache Kafka ......................... SKIPPED
[INFO] Integrations: Apache Mynewt ........................ SKIPPED
[INFO] Integrations: Apache Nifi .......................... SKIPPED
[INFO] Integrations: Apache Nifi: Processors .............. SKIPPED
[INFO] Integrations: Apache Nifi: NAR ..................... SKIPPED
[INFO] Integrations: Apache Karaf ......................... SKIPPED
[INFO] Integrations: Apache Karaf: ADS .................... SKIPPED
[INFO] Integrations: Apache Karaf: EtherNet/IP ............ SKIPPED
[INFO] Integrations: Apache Karaf: Modbus ................. SKIPPED
[INFO] Integrations: Apache Karaf: S7 ..................... SKIPPED
[INFO] Integrations: Apache Karaf: Simulated .............. SKIPPED
[INFO] Integrations: Apache Karaf: Demo Server ............ SKIPPED
[INFO] Integrations: Apache Calcite ....................... SKIPPED
[INFO] Examples ........................................... SKIPPED
[INFO] Examples: Protocol: Dummy .......................... SKIPPED
[INFO] Examples: Cloud: Azure IoT Hub ..................... SKIPPED
[INFO] Examples: Cloud: Google Cloud IoT Core ............. SKIPPED
[INFO] Examples: Connectivity: Kafka ...................... SKIPPED
[INFO] Examples: Connectivity: MQTT ....................... SKIPPED
[INFO] Examples: Edgent ................................... SKIPPED
[INFO] Examples: Hello OPM ................................ SKIPPED
[INFO] Examples: Storage: ElasticSearch ................... SKIPPED
[INFO] Examples: Hello-Webapp (root) ...................... SKIPPED
[INFO] Examples: Hello-Webapp: Client ..................... SKIPPED
[INFO] Examples: Hello-Webapp: Service .................... SKIPPED
[INFO] Examples: Hello-Webapp: Spring-Boot WAR ............ SKIPPED
[INFO] Examples: Hello-World PLC4X ........................ SKIPPED
[INFO] PLC4Cpp ............................................ SKIPPED
[INFO] PLC4Cpp: Libs ...................................... SKIPPED
[INFO] PLC4Cpp: Libs: Boost ............................... SKIPPED
[INFO] PLC4Cpp: API ....................................... SKIPPED
[INFO] PLC4Cpp: Protocols ................................. SKIPPED
[INFO] PLC4Cpp: Protocols: Driver-Bases ................... SKIPPED
[INFO] PLC4Cpp: Protocols: Driver-Base: Base .............. SKIPPED
[INFO] PLC4Cpp: Utils ..................................... SKIPPED
[INFO] Sandbox ............................................ SKIPPED
[INFO] Sandbox: Dynamic-Driver: (Base) .................... SKIPPED
[INFO] Sandbox: Dynamic-Driver: S7 ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:41 min
[INFO] Finished at: 2019-04-29T15:00:31+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.1:single (package-thrift-python) on project plc4x-tools-thrift: Failed to create assembly: Error creating assembly archive python: archive cannot be empty -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :plc4x-tools-thrift
Hope that helps
Julian
Am 29.04.19, 14:38 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
I just wanted to inform you that I just merged the feature/PLC4X-111-interop-server branch back to develop.
I greatly refactored the way the build works so it should be a lot simpler and produce less problems, especially for the platform-dependent c++ stuff.
Also did I update the main README with all the prerequisites on the different platforms (Tested with Mac, Linux (Ubuntu 18.04), Windows 10).
I guess over the weekend I probably did 20-30 full builds on every of the 3 platforms with multiple different JDK versions … also did I setup clean VMs (fleshly installed systems) for all of the environments, so I hopefully got all the prerequisites needed.
It would be super-great if you guys could give the build a spin on your systems:
mvnw clean install site -P with-cpp,with-python,with-proxies,with-sandbox
The above command should build EVERYTHING … probably a good idea to start this when starting the next Game Of Thrones episode that came out last night ;-)
Feedback greatly appreciated.
Now I’ll create a new feature branch and try to untangle the examples, integrations and sandbox modules so we have something to discuss.
Chris
Re: Major update to the build just merged to develop
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi chris,
form e there is an exception in the build with the following (truncated) output:
[INFO] --- maven-assembly-plugin:3.1.1:single (package-thrift-python) @ plc4x-tools-thrift ---
[INFO] Reading assembly descriptor: src/assembly/python.xml
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for PLC4X 0.4.0-SNAPSHOT:
[INFO]
[INFO] PLC4X .............................................. SUCCESS [ 38.489 s]
[INFO] Protocols .......................................... SUCCESS [ 3.410 s]
[INFO] Protocols: Test-Utils .............................. SUCCESS [ 11.189 s]
[INFO] Protocols: KNXNet-IP ............................... SUCCESS [ 24.445 s]
[INFO] Protocols: S7 ...................................... SUCCESS [ 43.319 s]
[INFO] Protocols: Proxy ................................... SUCCESS [ 4.481 s]
[INFO] PLC4J .............................................. SUCCESS [ 2.941 s]
[INFO] PLC4J: Utils ....................................... SUCCESS [ 2.219 s]
[INFO] PLC4J: Utils: Test Utils ........................... SUCCESS [ 5.051 s]
[INFO] PLC4J: API ......................................... SUCCESS [ 9.116 s]
[INFO] PLC4J: Protocols ................................... SUCCESS [ 3.506 s]
[INFO] PLC4J: Protocols: Driver-Bases ..................... SUCCESS [ 2.042 s]
[INFO] PLC4J: Protocol: Driver-Base: Base ................. SUCCESS [ 23.471 s]
[INFO] PLC4J: Protocol: Driver-Base: Test ................. SUCCESS [ 7.968 s]
[INFO] PLC4J: Protocol: ADS ............................... SUCCESS [ 17.576 s]
[INFO] PLC4J: Protocol: Driver-Base: TCP .................. SUCCESS [ 4.352 s]
[INFO] PLC4J: Protocol: Driver-Base: Serial ............... SUCCESS [ 4.525 s]
[INFO] PLC4J: Drivers ..................................... SUCCESS [ 2.148 s]
[INFO] PLC4J: Driver: ADS ................................. SUCCESS [ 25.162 s]
[INFO] PLC4J: Protocol: Ethernet/IP ....................... SUCCESS [ 4.300 s]
[INFO] PLC4J: Driver: Ethernet/IP ......................... SUCCESS [ 6.496 s]
[INFO] PLC4J: Protocol: Modbus ............................ SUCCESS [ 6.726 s]
[INFO] PLC4J: Driver: Modbus .............................. SUCCESS [ 23.552 s]
[INFO] PLC4J: Protocol: ISO on TCP ........................ SUCCESS [ 7.007 s]
[INFO] PLC4J: Protocol: ISO TP ............................ SUCCESS [ 7.962 s]
[INFO] PLC4J: Protocol: S7 ................................ SUCCESS [ 14.038 s]
[INFO] PLC4J: Driver: S7 .................................. SUCCESS [ 9.578 s]
[INFO] PLC4J: Driver: Simulated ........................... SUCCESS [ 17.948 s]
[INFO] PLC4J: Protocol: Driver-Base: Raw Socket ........... SUCCESS [ 4.128 s]
[INFO] PLC4J: Protocol: Delta-V ........................... SUCCESS [ 7.550 s]
[INFO] PLC4J: Protocol: Benchmarks ........................ SUCCESS [ 5.732 s]
[INFO] PLC4J: Utils: Connection Pool ...................... SUCCESS [ 6.509 s]
[INFO] PLC4J: Utils: Object PLC Mapping ................... SUCCESS [ 11.039 s]
[INFO] PLC4J: Utils: Raw-Sockets .......................... SUCCESS [ 6.195 s]
[INFO] PLC4J: Utils: Scraper .............................. SUCCESS [ 10.349 s]
[INFO] Tools .............................................. SUCCESS [ 2.098 s]
[INFO] Tools: Thrift ...................................... FAILURE [02:11 min]
[INFO] PLC4J: Utils: Interop-Server ....................... SKIPPED
[INFO] PLC4PY ............................................. SKIPPED
[INFO] Integrations ....................................... SKIPPED
[INFO] Integrations: Apache Brooklyn ...................... SKIPPED
[INFO] Integrations: Apache Camel ......................... SKIPPED
[INFO] Integrations: Apache Edgent ........................ SKIPPED
[INFO] Integrations: Apache Kafka ......................... SKIPPED
[INFO] Integrations: Apache Mynewt ........................ SKIPPED
[INFO] Integrations: Apache Nifi .......................... SKIPPED
[INFO] Integrations: Apache Nifi: Processors .............. SKIPPED
[INFO] Integrations: Apache Nifi: NAR ..................... SKIPPED
[INFO] Integrations: Apache Karaf ......................... SKIPPED
[INFO] Integrations: Apache Karaf: ADS .................... SKIPPED
[INFO] Integrations: Apache Karaf: EtherNet/IP ............ SKIPPED
[INFO] Integrations: Apache Karaf: Modbus ................. SKIPPED
[INFO] Integrations: Apache Karaf: S7 ..................... SKIPPED
[INFO] Integrations: Apache Karaf: Simulated .............. SKIPPED
[INFO] Integrations: Apache Karaf: Demo Server ............ SKIPPED
[INFO] Integrations: Apache Calcite ....................... SKIPPED
[INFO] Examples ........................................... SKIPPED
[INFO] Examples: Protocol: Dummy .......................... SKIPPED
[INFO] Examples: Cloud: Azure IoT Hub ..................... SKIPPED
[INFO] Examples: Cloud: Google Cloud IoT Core ............. SKIPPED
[INFO] Examples: Connectivity: Kafka ...................... SKIPPED
[INFO] Examples: Connectivity: MQTT ....................... SKIPPED
[INFO] Examples: Edgent ................................... SKIPPED
[INFO] Examples: Hello OPM ................................ SKIPPED
[INFO] Examples: Storage: ElasticSearch ................... SKIPPED
[INFO] Examples: Hello-Webapp (root) ...................... SKIPPED
[INFO] Examples: Hello-Webapp: Client ..................... SKIPPED
[INFO] Examples: Hello-Webapp: Service .................... SKIPPED
[INFO] Examples: Hello-Webapp: Spring-Boot WAR ............ SKIPPED
[INFO] Examples: Hello-World PLC4X ........................ SKIPPED
[INFO] PLC4Cpp ............................................ SKIPPED
[INFO] PLC4Cpp: Libs ...................................... SKIPPED
[INFO] PLC4Cpp: Libs: Boost ............................... SKIPPED
[INFO] PLC4Cpp: API ....................................... SKIPPED
[INFO] PLC4Cpp: Protocols ................................. SKIPPED
[INFO] PLC4Cpp: Protocols: Driver-Bases ................... SKIPPED
[INFO] PLC4Cpp: Protocols: Driver-Base: Base .............. SKIPPED
[INFO] PLC4Cpp: Utils ..................................... SKIPPED
[INFO] Sandbox ............................................ SKIPPED
[INFO] Sandbox: Dynamic-Driver: (Base) .................... SKIPPED
[INFO] Sandbox: Dynamic-Driver: S7 ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:41 min
[INFO] Finished at: 2019-04-29T15:00:31+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.1:single (package-thrift-python) on project plc4x-tools-thrift: Failed to create assembly: Error creating assembly archive python: archive cannot be empty -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :plc4x-tools-thrift
Hope that helps
Julian
Am 29.04.19, 14:38 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
I just wanted to inform you that I just merged the feature/PLC4X-111-interop-server branch back to develop.
I greatly refactored the way the build works so it should be a lot simpler and produce less problems, especially for the platform-dependent c++ stuff.
Also did I update the main README with all the prerequisites on the different platforms (Tested with Mac, Linux (Ubuntu 18.04), Windows 10).
I guess over the weekend I probably did 20-30 full builds on every of the 3 platforms with multiple different JDK versions … also did I setup clean VMs (fleshly installed systems) for all of the environments, so I hopefully got all the prerequisites needed.
It would be super-great if you guys could give the build a spin on your systems:
mvnw clean install site -P with-cpp,with-python,with-proxies,with-sandbox
The above command should build EVERYTHING … probably a good idea to start this when starting the next Game Of Thrones episode that came out last night ;-)
Feedback greatly appreciated.
Now I’ll create a new feature branch and try to untangle the examples, integrations and sandbox modules so we have something to discuss.
Chris