Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 274964 - Make dev-java/avalon-logkit build with >=virtual/jdk-1.6
Summary: Make dev-java/avalon-logkit build with >=virtual/jdk-1.6
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Java (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Java team
URL: N/A
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-21 17:18 UTC by Robert Bradbury
Modified: 2009-06-21 18:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Emerge --info (EMG.lst,3.85 KB, text/plain)
2009-06-21 17:18 UTC, Robert Bradbury
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Bradbury 2009-06-21 17:18:04 UTC
Recent changes to avalon-logkit ebuild require re-installation of dev-java-1.5 (for those of us who have upgraded beyond 1.5, its "history" and we really don't want to install 50MB of software for just one package if we can avoid it).

The comment in the ebuild is rather non-explanatory, e.g.
"# Doesn't like 1.6 changes to JDBC"

My read of the sources is that there are 4 JDBC's (for mssqlserer, mysql, oracle and postgresql).  The question is whether the problems effect *all* JDBCs or just one or several?  And will the problem be fixed by an upgrade to avalon-logkit and/or one or more of the jdbc's?  Uninstalling avalon-logkit appears to be unworkable as commons-logging depends on it and then ant depends on that.

Reproducible: Always

Steps to Reproduce:
1. emerge -pv avalon-logkit



Actual Results:  
Wants to install sun-jdk-1.5.0.19 (as a new slot beside 1.6.0.14)

Expected Results:  
avalon-logkit and/or the jdbc packages should be upgraded to allow avalon-logkit to work on more current versions of the JDK.
Comment 1 Robert Bradbury 2009-06-21 17:18:51 UTC
Created attachment 195367 [details]
Emerge --info

Emerge --info for system
Comment 2 Petteri Räty (RETIRED) gentoo-dev 2009-06-21 18:40:14 UTC
(In reply to comment #0)
> Recent changes to avalon-logkit ebuild require re-installation of dev-java-1.5
> (for those of us who have upgraded beyond 1.5, its "history" and we really
> don't want to install 50MB of software for just one package if we can avoid
> it).

There are no recent changes to avalon-logkit that would make it require 1.5. It has required 1.4 or 1.5 for years. Java SE is not API forwards compatible so avalon-logkit doesn't compile with 1.6:

compile:
    [mkdir] Created dir: /var/tmp/portage/dev-java/avalon-logkit-2.1-r3/work/avalon-logkit-2.1/target/classes
    [javac] Compiling 61 source files to /var/tmp/portage/dev-java/avalon-logkit-2.1-r3/work/avalon-logkit-2.1/target/classes
    [javac] /var/tmp/portage/dev-java/avalon-logkit-2.1-r3/work/avalon-logkit-2.1/src/java/org/apache/log/output/db/DefaultDataSource.java:31: org.apache.log.output.db.DefaultDataSource is not abstract and does not override abstract method isWrapperFor(java.lang.Class) in java.sql.Wrapper
    [javac] public class DefaultDataSource
    [javac]        ^
    [javac] 1 error

> 
> My read of the sources is that there are 4 JDBC's (for mssqlserer, mysql,
> oracle and postgresql).  The question is whether the problems effect *all*
> JDBCs or just one or several?  And will the problem be fixed by an upgrade to
> avalon-logkit and/or one or more of the jdbc's?  Uninstalling avalon-logkit
> appears to be unworkable as commons-logging depends on it and then ant depends
> on that.
> 

If you don't want to install avalon-logkit then turn off the avalon-logkit USE flag in commons-logging.

> 
> Expected Results:  
> avalon-logkit and/or the jdbc packages should be upgraded to allow
> avalon-logkit to work on more current versions of the JDK.
> 

This means modifying upstream code but I think avalon is pretty much dead upstream so if you want this to happen please create a patch that makes avalon-logkit work with 1.6. For Gentoo requiring an older JDK is expected behavior and as such marking this as upstream. If you make a patch please reopen, otherwise we will visit this issue when 1.5 EOLs as at that point we will have to make avalon-logkit work with 1.6 or drop it altogether.