maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SebbASF (JIRA)" <>
Subject [jira] Commented: (MPIR-80) Add Java requirements to the Dependency Report
Date Mon, 05 Jul 2010 10:54:32 GMT


SebbASF commented on MPIR-80:

The "target" Java version needs to be added to the dependencies report, because the JVM version
is a run-time dependency.
The "source" Java version should also be included as it affects the compile-time dependencies.

It would be helpful to add both the "source" and "target" Java versions to the project report.

What's important to report are the *intended* source and target Java versions, as defined
by the POM.

I think it would be unsafe to examine the bytecode of whatever is in the local repo, as that
may well be out of date.
Besides, AFAIK that can not be used to determine the "source" version.

> Add Java requirements to the Dependency Report
> ----------------------------------------------
>                 Key: MPIR-80
>                 URL:
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: New Feature
>          Components: dependencies, summary
>    Affects Versions: 2.0.1
>            Reporter: Niall Pemberton
>         Attachments: maven-projectinfo-dependency-java-v3.patch, maven-projectinfo-dependency-java.patch,
> It would be nice to add a section to the dependency report showing the java version requirements.
> Attaching a patch which discovers the java version and compiler options from the java-compiler-plugin
configuration and outputs a "Java Version" section. Has an option to configure whether or
not this section is shown (default to false).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message