Bug 1375362 - atinject built with newer Java target prevents maven from working
Summary: atinject built with newer Java target prevents maven from working
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atinject
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Java maintainers
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-12 20:46 UTC by Christopher Tubbs
Modified: 2020-01-17 16:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-17 16:05:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
CentOS 11445 0 None None None 2016-09-12 20:46:56 UTC

Description Christopher Tubbs 2016-09-12 20:46:57 UTC 
Description of problem:
atinject is compiled with a default Java target (which appears to be 1.7), rather than explicitly specifying a target.

This prevents maven from working when building a Java 6 project with the system-provided OpenJDK 6.

Version-Release number of selected component (if applicable):
atinject-1-13.20100611svn86.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. export JAVA_HOME=/usr/lib/jvm/java-1.6.0
2. export PATH=$JAVA_HOME/bin:$PATH # because some plugins use path
3. mvn package

Actual results:
Long error message with: Exception in thread "main" java.lang.UnsupportedClassVersionError: javax/inject/Provider : Unsupported major.minor version 51.0

Expected results:
Project should build.

Additional info:
This was fixed in Fedora: http://pkgs.fedoraproject.org/cgit/rpms/atinject.git/commit/?id=a7edf577
Comment 7 Joe Orton 2020-01-17 16:05:10 UTC 
Rebuilding the Java packages with anything other than OpenJDK 7 is not supported and will not be supported in RHEL7.
Note You need to log in before you can comment on or make changes to this bug.