Project

General

Profile

Actions

bug #6023

closed

configuration problems with maven-antrun-plugin

Added by Andreas Kohlbecker over 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
New
Category:
cdmlib
Target version:
Start date:
07/29/2016
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Found in Version:

Description

Problems

1.

Running mvn clean install with java 1.8 (oracle) on cdmlib fails in cdmlib-model with

The type java.util.Comparator cannot be resolved. It is indirectly referenced from required .class files

However, no problems with java 1.7

The hint on http://www.quweiji.com/the-type-java-lang-object-cannot-be-resolved-it-is-indirectly-referenced/ suggests to look for the cause of this in possible parallel use of different jdk versions in the same project.

2.

Running mvn clean install with any java version on cdmlib report the warning:

[INFO] --- maven-antrun-plugin:1.3:run (aspectj-main) @ cdmlib-model ---
[INFO] Executing tasks
[iajc] warning build config error: skipping missing, empty or corrupt aspectpath entry: /var/lib/jenkins/.m2/repository/org/springframework/org.springframework.aspects/4.2.4.RELEASE/org.springframework.aspects-4.2.4.RELEASE.jar

Related issues

Related to Edit - feature request #4716: Other dependencies to be updatedClosedAndreas Müller11/26/201502/01/2016

Actions
Blocks Edit - bug #6025: Remaining open issues for cdmlib-dbNewAndreas Müller08/01/2016

Actions
Actions #1

Updated by Andreas Kohlbecker over 5 years ago

Actions #2

Updated by Andreas Kohlbecker over 5 years ago

  • Description updated (diff)
Actions #3

Updated by Andreas Kohlbecker over 5 years ago

This problem is related to

using iajc with java 1.8 JDK — Comparator cannot be resolved to a type: "It came down to the existence of a copy of aspectjtools.jar within my %ANT_HOME%\lib folder. This JAR had been placed there many, many (many!) years ago. It happened to be the AspectJ 1.6 version of the JAR and its existence there caused ant to use that version even though our build.xml file had been modified at some point to specify the path to AspectJ"

I hope that helps ...

Actions #4

Updated by Andreas Kohlbecker over 5 years ago

see branch jdk18-compatibility

Actions #6

Updated by Andreas Müller over 5 years ago

  • Blocks bug #6025: Remaining open issues for cdmlib-db added
Actions #8

Updated by Andreas Kohlbecker about 5 years ago

  • Status changed from New to In Progress
  • Target version set to Release 4.4
Actions #9

Updated by Andreas Kohlbecker about 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 50
Actions #10

Updated by Andreas Müller about 5 years ago

  • Status changed from Resolved to Closed
  • Assignee changed from Andreas Müller to Andreas Kohlbecker

Seems to work. I also tested the latest build on a machine with java 1.7 installed (pesihpc) and got no problems.

Actions #11

Updated by Andreas Müller about 5 years ago

  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF