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 2019/10/29 20:34:31 UTC
[plc4x] branch develop updated: PLC4X-147 - Make PLC4X build with
Java 13 - Updated some plugins to make the build work with Java 13 --
Jacoco -- Groovy - Fixed one old assembly plugin version
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
The following commit(s) were added to refs/heads/develop by this push:
new 4dcd81a PLC4X-147 - Make PLC4X build with Java 13 - Updated some plugins to make the build work with Java 13 -- Jacoco -- Groovy - Fixed one old assembly plugin version
4dcd81a is described below
commit 4dcd81adf6e9f9e3557274733be29f974300f0c5
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Tue Oct 29 21:34:24 2019 +0100
PLC4X-147 - Make PLC4X build with Java 13
- Updated some plugins to make the build work with Java 13
-- Jacoco
-- Groovy
- Fixed one old assembly plugin version
NO JIRA:
- Added some more documentation on the windows setup
---
README.md | 12 ++++++++----
plc4j/utils/interop/pom.xml | 2 +-
pom.xml | 6 +++---
3 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/README.md b/README.md
index b909fde..e00d5dd 100644
--- a/README.md
+++ b/README.md
@@ -136,24 +136,28 @@ Some tools need to be installed before being able to build on Windows:
* Python 2.7 (for `with-python`, `with-proxies` profiles)
* Dotnet (for `with-dotnet` profiles)
-He have tested WinBuilds with the bundle of: http://win-builds.org/doku.php/download_and_installation_from_windows
+He have tested `WinBuilds` with the bundle of: http://win-builds.org/doku.php/download_and_installation_from_windows
+Run the installer as "Administrator" or you won't be able to install it to "C:\Program Files" or the 32 Bit counterpart.
When running the installer, make sure to select the options:
* Native Windows
* x86_64
Not quite sure which elements are really needed, better just install all of them.
+If the installer fails to do something complaining about having to use a different mirror, enter "http://win-builds.org/1.5.0" as mirror address.
WARNING: If you don't use the installer version of the distribution. The build will probably fail and it will be pretty
impossible to see the problem. When manually executing the command, a popup will appear complaining about not being able
to find some DLL. So if you are having these problems, please try using the installer instead of manually unpacking
the archive.
-For Bison, please download the Setup installer version from here: http://gnuwin32.sourceforge.net/packages/bison.htm (When using the zip version the bison.exe couldn't find some DLL files)
+For `Bison`, please download the Setup installer version from here: http://gnuwin32.sourceforge.net/packages/bison.htm (When using the zip version the bison.exe couldn't find some DLL files)
It seems the official 2.4.1 version has issues when installed in a directory which's path contains spaces. Please make sure you replace the exe with a patched version form here: http://marin.jb.free.fr/bison/bison-2.4.1-modified.zip
(More infos on this issue here: https://sourceforge.net/p/gnuwin32/bugs/473/)
-Please download the Flex compiler from here: http://gnuwin32.sourceforge.net/packages/flex.htm (Ideally download the binary zip distribution)
+Please download the `Flex` compiler from here: http://gnuwin32.sourceforge.net/packages/flex.htm (Ideally download the binary zip distribution)
-You can get Python from here: https://www.python.org/downloads/release/python-2716/
+You can get `Python` from here: https://www.python.org/downloads/release/python-2716/
+
+For `.Net`, you need the `Developer Pack` in order to build .Net applications. So be sure to get a reasonably fresh installation from https://dotnet.microsoft.com
Make sure the `bin` directories of containing the executables `mingw32-make.exe`, `bison.exe` and `flex.exe` are all on your systems `PATH`.
diff --git a/plc4j/utils/interop/pom.xml b/plc4j/utils/interop/pom.xml
index 14d2e06..ab3f76c 100644
--- a/plc4j/utils/interop/pom.xml
+++ b/plc4j/utils/interop/pom.xml
@@ -116,7 +116,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
- <version>2.5.3</version>
+ <version>3.1.1</version>
<configuration>
<!-- get all project dependencies -->
<!-- <descriptorRefs>-->
diff --git a/pom.xml b/pom.xml
index 5f62ebf..36fc2e0 100644
--- a/pom.xml
+++ b/pom.xml
@@ -128,7 +128,7 @@
<equalsverifier.version>3.0.2</equalsverifier.version>
<findbugs.version>3.0.1</findbugs.version>
<freemarker.version>2.3.28</freemarker.version>
- <groovy.version>2.5.3</groovy.version>
+ <groovy.version>2.5.8</groovy.version>
<gson.version>2.8.5</gson.version>
<guava.version>27.0.1-jre</guava.version>
<hamcrest.version>1.3</hamcrest.version>
@@ -1167,7 +1167,7 @@
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
- <version>0.8.2</version>
+ <version>0.8.5</version>
</plugin>
<plugin>
@@ -1516,7 +1516,7 @@
<plugin>
<groupId>org.codehaus.gmaven</groupId>
<artifactId>groovy-maven-plugin</artifactId>
- <version>2.1</version>
+ <version>2.1.1</version>
<executions>
<!-- Do some pre-build checks and report any findings to the user -->
<execution>