Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Maven dependencies are downloaded with wrong classifier

See original GitHub issue

This might be maven knowledge problem, but maybe not. from my pom.xml

<properties>
	<maven.compiler.source>1.8</maven.compiler.source>
	<maven.compiler.target>1.8</maven.compiler.target>
	<sfm.version>7.0.3</sfm.version>
</properties>
<dependencyManagement>
	<dependencies>
		<dependency>
			<groupId>org.simpleflatmapper</groupId>
			<artifactId>sfm-csv</artifactId>
			<version>${sfm.version}</version>
		</dependency>
	</dependencies>
</dependencyManagement>
<dependencies>
	<dependency>
		<groupId>org.simpleflatmapper</groupId>
		<artifactId>sfm-csv</artifactId>
	</dependency>
</dependencies>

Maven version 3.6.1.

During run time I get error: java.lang.UnsupportedClassVersionError: org/simpleflatmapper/util/Enumerable has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0

As one can see from image dependencies has wrong classifier: SFM-JDK9

Is this problem on my end?

Issue Analytics

State:
Created 4 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

10reactions

Mincolcommented, Aug 21, 2019

Yes, this is IntelliJ Idea. Fix for me os to change JDK for Importer to be java version 1.8 JDKforImporter

Can you explain me, please, why having there Java 11 downloaded classifier jdk9? Thank you for enlightening me.

0reactions

arnaudrogercommented, Sep 2, 2019

that should be fixed in 8 https://simpleflatmapper.org/2019/09/01/v8.0.0.html I changed the build and I don’t use the classifier anymore, instead it generate different artifactId for each jre version

Top Results From Across the Web

Maven downloads the wrong version - Stack Overflow

I've looked for that version 75.1.1 and it's mentionned nowhere in the project. The dependency to the other project is defined only at...

How to Resolve a Version Collision of Artifacts in Maven

Then, we'll see how to prevent getting the wrong version of an artifact with either exclusion or dependency management.

Gradle 2.2.1 seems to ignore my classifier on my dependency ...

It's like the classifier was totally forgotten on the lookup, then somehow it started searching for 3.0.5 in a totally different repository, and ......

Apache Maven Dependency Plugin – dependency:get

The artifactId of the artifact to download. Ignored if artifact is used. User property is: artifactId . <classifier>, String ...

IntelliJ uses wrong version of Maven-managed dependency

Classifier - This might be new for 2.1. Currently the M2 resolver doesn't use it. The current documentation suggest its use for additional ......