Maven 2 & 3

maven version insistence based on wrong variable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.4
  • Fix Version/s: 2.0.5
  • Component/s: Bootstrap & Build
  • Labels:
    None
  • Environment:
    OS : ubuntu dapper
    java vm : SableVM 1.11.3
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

MavenCli does

if (System.getProperty("java.class.version", "44.0").compareTo("48.0") < 0) //then echo "sorry we need version 1.4"

however java.class.version is the binary packaging format for the classes, not the supported API. java.version is the supported api, for which sable returns 1.4.2. So the process aborts out, wanting the 1.4 API, when it has 1.4 API (sable has 46.0 instead of 48.0 as the class packaging format used)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jörg Schaible added a comment -

Be careful with java.version also, see comments on XSTR-249. XStream uses therefore java.specification.version now.

Show
Jörg Schaible added a comment - Be careful with java.version also, see comments on XSTR-249 . XStream uses therefore java.specification.version now.
Hide
Permalink
Vincent Siveton added a comment -

Fixed using "java.specification.version" instead of "java.class.version"

Show
Vincent Siveton added a comment - Fixed using "java.specification.version" instead of "java.class.version"

People

  • Assignee:
    Vincent Siveton
    Reporter:
    j
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: