You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by cd...@apache.org on 2020/05/22 14:31:53 UTC
[plc4x] branch develop updated (b027126 -> 8c368a0)
This is an automated email from the ASF dual-hosted git repository.
cdutz pushed a change to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git.
from b027126 - Explicitly set the _allow_illegal_access_reflection_in_tests profile to disabled to skip the detection on the site build node
new 21f08e4 - Explicitly set the _allow_illegal_access_reflection_in_tests profile to disabled to skip the detection on the site build node
new 8c368a0 - Moved the disabling of the java9-and-above profile to another step in the build
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
Jenkinsfile | 10 +++++-----
src/site/asciidoc/developers/preparing/index.adoc | 14 ++++++++++++--
2 files changed, 17 insertions(+), 7 deletions(-)
[plc4x] 01/02: - Explicitly set the
_allow_illegal_access_reflection_in_tests profile to disabled to skip the
detection on the site build node
Posted by cd...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git
commit 21f08e416a210cceb2bb49769899e6e39b3a4df9
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Fri May 22 16:26:06 2020 +0200
- Explicitly set the _allow_illegal_access_reflection_in_tests profile to disabled to skip the detection on the site build node
---
src/site/asciidoc/developers/preparing/index.adoc | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/src/site/asciidoc/developers/preparing/index.adoc b/src/site/asciidoc/developers/preparing/index.adoc
index f70797f..3e4df82 100644
--- a/src/site/asciidoc/developers/preparing/index.adoc
+++ b/src/site/asciidoc/developers/preparing/index.adoc
@@ -23,14 +23,24 @@ However when building PLC4X there are some requirements the build is expecting y
However this greatly depends on which parts you want to build.
The `Java` modules hereby probably have the least demanding requirements.
-In order to build at all you are required to have `Java 8` installed on your machine.
+In order to build most Java parts of `PLC4X` you are required to have at least `Java 8` installed on your machine.
+Some integration modules and some other languages however may add some additional constraints to this.
-TIP: We have tested the build with Java 8 up to Java 13 (Latest version at the time of writing this document).
+For example if you are using the `with-logstash` module to build the Logstash integration, you are required to use `Java 8` to `Java 11`, below and above doesn't work.
+On the other side as soon as you're building with the `with-c`, `with-cpp` or `with-proxies` you need to use at least `Java 11` as the `cmake-maven-plugin` requires at least this version.
+
+TIP: Currently Java 11 is the sweet-spot for being able to build all parts of PLC4X.
+
+TIP: We have tested the build with Java 8 up to Java 14 (Latest version at the time of writing this document).
If a new version comes out, please give us a little time to verify and handle any related issues.
We'll probably fix them as soon as possible.
However in the past with Oracle's new release strategy, there have been a few bumps on the road.
+Also will PLC4X build with any Maven version starting with `Maven 3.3.0` however the `with-c`, `with-cpp` and `with-proxies` profiles require at least `Maven 3.6` as the `cmake-maven-plugin` requires this.
+
+TIP: Currently Maven 3.6 and above is required for being able to build all parts of PLC4X.
+
[width=100%]
|===
| Profile | Description | Requirements
[plc4x] 02/02: - Moved the disabling of the java9-and-above profile
to another step in the build
Posted by cd...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/plc4x.git
commit 8c368a0764a37a354b80f82dc1075fd2a822d3ae
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Fri May 22 16:31:46 2020 +0200
- Moved the disabling of the java9-and-above profile to another step in the build
---
Jenkinsfile | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Jenkinsfile b/Jenkinsfile
index c46b32a..729dd37 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -173,7 +173,10 @@ pipeline {
steps {
echo 'Building Site'
//sh 'mvn -P${JENKINS_PROFILE},skip-prerequisite-check,with-proxies,with-logstash site'
- sh 'mvn -P${JENKINS_PROFILE},skip-prerequisite-check,with-logstash site -pl .'
+ // Explicitly deselecting the "_allow_illegal_access_reflection_in_tests"
+ // profile as there seem to be problems on the site building node to detect the java version.
+ // In this case we don't really care as no unit- or integration-tests are being executed.
+ sh 'mvn -P${JENKINS_PROFILE},skip-prerequisite-check,with-logstash,!_allow_illegal_access_reflection_in_tests site -pl .'
}
}
@@ -215,10 +218,7 @@ pipeline {
// Unstash the previously stashed site.
unstash 'plc4x-site'
// Publish the site with the scm-publish plugin.
- // Explicitly deselecting the "_allow_illegal_access_reflection_in_tests"
- // profile as there seem to be problems on the site building node to detect the java version.
- // In this case we don't really care as no unit- or integration-tests are being executed.
- sh 'mvn -f jenkins.pom -X -P deploy-site,!_allow_illegal_access_reflection_in_tests scm-publish:publish-scm'
+ sh 'mvn -f jenkins.pom -X -P deploy-site scm-publish:publish-scm'
// Clean up the snapshots directory (freeing up more space after deploying).
dir("target/staging") {