Try running the following commands and examine the output:
$ mvn dependency:tree
$ mvn help:effective-pom
Look for commons-lang, maybe something will draw your attention like excludes or dependency overrides. Also, is:
$ mvn dependency:copy-dependencies
copying commons-lang JAR to your target?
Try running the following commands and examine the output:
$ mvn dependency:tree
$ mvn help:effective-pom
Look for commons-lang, maybe something will draw your attention like excludes or dependency overrides. Also, is:
$ mvn dependency:copy-dependencies
copying commons-lang JAR to your target?
Adding following dependency to pom.xml in dependencies tag helped me:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-lang3</artifactId>
<version>3.1</version>
</dependency>
Org.apache.commons.lang is internal and is not available for export
Error:(13, 32) error: package org.apache.commons.lang3 does not exist
Getting "org.apache.commons.lang does not exist" error while updating jasper to 6.20.5 - Products - Jaspersoft Community
Camunda Upgrade - org.apache.commons.lang error
If i understand correctly, you added the jar in your eclipse build path. However, this usually doesn't mean you added it to you gradle build script, which means gradle doesn't know about the commons-lang jar file, only eclipse does.
To add it to gradle, you should add it to the build.gradle file, more or less as follows :
dependencies {
compile group: 'org.apache.commons', name: 'commons-lang3', version: '3.3.2'
}
Maybe you could try using a gradle plugin for ecplise, like https://github.com/spring-projects/eclipse-integration-gradle/ to automate or make easier to keep ecplise and the gradle script in sync.
Make sure that the classpath for your build script is properly defined.