I have selenium tests with Sikuli.
When I was using sikuli 1.x all worked fine.
The issue started when I moved to sikuli 2.x
I import Sikuli by maven:
<dependency>
<groupId>com.sikulix</groupId>
<artifactId>sikulixapi</artifactId>
<version>2.0.5</version>
</dependency>
I tried to run this with Jenkins on CentOS7 and AWS linux.
I got on both a runtime error:
GLIBC_2.27' not found (required by /root/.Sikulix/SikulixLibs/libopencv_java430.so)
Did someone see and solve this issue?
Thanks a head for any help
Lior
My application is using Log4j 2.11.1 now. Because of the Log4j security vulnerabilities reported a couple of days ago, I need to update Log4j to 2.15.0. But it fails when I deploy my application on a Linux server.
Here is the error message:
[ERROR] Failed to execute goal on project ***: Could not resolve
dependencies for project ***:1.0-SNAPSHOT: Failed to collect
dependencies at org.apache.logging.log4j:log4j-api:jar:2.15.0: Failed
to read artifact descriptor for
org.apache.logging.log4j:log4j-api:jar:2.15.0: Could not transfer
artifact org.apache.logging.log4j:log4j-api:pom:2.15.0 from/to central
(https://repo1.maven.org/maven2):
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target -> [Help 1]
I've added the certificate of Maven 2 to my Java keystore, but it does not work. My Java version is 1.8.181.
I had log4j-core and log4j-api which needed to be updated. It is a similar case as you had, deployment on as a Linux server. It works for me.
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-1.2-api</artifactId>
<version>2.15.0</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.15.0</version>
</dependency>
I added these dependencies and updated the maven project (in the Eclipse IDE, right click on Project → Go to Maven → Update Project).
Log4j Vulnerability issue with later versions
The version Log4j 2.15.0 was released as a possible fix for this critical vulnerability, but this version was found to be still vulnerable (by Apache Software Foundation).
Solution: Log4j 2.16.0 fixes this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
You can have a look at Maven, Ivy, Gradle, and SBT Artifacts.
In my case I had to switch from 1.2.x version to 2.16.0.
You can try using this dependency:
<dependencies>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-1.2-api</artifactId>
<version>2.16.0</version>
</dependency>
</dependencies>
As Log4j security vulnerabilities are addressed in log4j-core, please try the latest version of log4j-core using a Maven dependency:
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.16.0</version>
</dependency>
Reference - Maven Repository: log4j
Regarding the exception you are facing, this may help you -
Java: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Specifically for a "PKIX path building failed" error in Maven:
If you are on Windows and your IT folks have added transparent proxies that intercept SSL traffic, you'll want to set MAVEN_OPTS to the following:
-Djavax.net.ssl.keyStoreType=Windows-MY -Djavax.net.ssl.trustStoreType=Windows-ROOT
This will direct Maven to use the Windows trust store when vetting SSL certificates issued internally by your IT staff.
If it is a transparent proxy peeking at SSL, but you're not in Windows, you may need to add that certificate to your JVMs trusted keystore, as the JVM options I have only work on Windows.
I faced the same problem with the following dependency:
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j</artifactId>
<version>2.15.0</version>
</dependency>
I replaced the above dependency with:
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-1.2-api</artifactId>
<version>2.15.0</version>
</dependency>
It works OK.
Does log4j2.8.2.jar work with JDK 1.7.
How to find the supported jdk version for a given jar file ? In my case i want to find the supported jdk version for log4j 2.8.2.jar.
https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j/2.8.2
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j</artifactId>
<version>2.8.2</version>
<type>pom</type>
</dependency>
I think Java 7 is supported up to 2.12.1
https://logging.apache.org/log4j/2.x/
Requirements
Log4j 2.13.0 and greater require Java 8. Version 2.4 through 2.12.1 required Java 7 and versions 2.0-alpha1 to 2.3 required Java 6. Some features require optional dependencies; the documentation for these features specifies the dependencies.
I'm new in Spark. I installed jdk8 and eclipse (mars) in debian 8. And installes Spark1.4.0 and used sbt/sbt assembly command to get all required. COuld anyone tell me how to write a simple hello program in spark using eclipse ide which need to coded in java. or tell me a url to do the same. I need a step-by-step help.
Thank you in advance
You can make a maven project and add spark 1.4 maven dependency as follow.
<dependency>
<groupId>org.apache.spark</groupId>
<artifactId>spark-core_2.10</artifactId>
<version>1.4.0</version>
</dependency>
And start coding in eclipse ide.
you can follow this or this and here is the java wordcount in spark example code
The link is for scala, but the same goes for java. hope it will help.
I try to create a JSF app with richfaces but I get a ClassNotFoundException as soon as I deploy the application on JBoss 5.1 (Java 1.6) (I cannot switch another JBoss version)
I defined the dependencies in the pom as follows:
<dependencies>
<dependency>
<groupId>org.richfaces</groupId>
<artifactId>richfaces-bom</artifactId>
<version>${org.richfaces.bom.version}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.richfaces.ui</groupId>
<artifactId>richfaces-components-ui</artifactId>
</dependency>
<dependency>
<groupId>org.richfaces.core</groupId>
<artifactId>richfaces-core-impl</artifactId>
</dependency>
...
<properties>
<org.richfaces.bom.version>4.1.0.Final</org.richfaces.bom.version>
</properties>
Any idea?
D3
Jboss 5.1 supports JSF 1.2 and not JSF 2.x. Rich Faces 4.x is built to work on JSF 2.x
You are using Jboss 5.1, but defining the dependencies as Rich Faces 4.x.
Since you are telling that you cannot switch to another Jboss version(I assume higher versions), you must think of coming down to RichFaces 3.x